사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Open one real PR whose title and description a busy reviewer can read in ten seconds.
Steps
- Check if a PR already exists for this branch (
gh pr list --head <branch>). If it does, update it. - Diff the branch against its base, usually
origin/main. Confirm the diff matches the goal and holds nothing unrelated. - Read the titles of a few recently merged PRs and copy their format.
- Write a title that says what changed for the user and why it matters, not which function moved. Example: "Cut websocket frames by 70% with compression" beats "Negotiate permessage-deflate".
- Write the description in this order:
- The problem, in one or two plain sentences taken from the user's request.
- The fix, in one or two sentences.
- One line on how it was proven, if you have proof.
- A closing line:
Created with <model> in <harness>.Use the model name the harness reports. If it reports none, name only the harness.
- Scan the title, body and any attachments for secrets, tokens, private paths and personal data. Remove them.
- Create the PR as ready for review, not a draft, so review bots run.
- Print the PR URL that GitHub returned.
Stop when
- GitHub returned a PR URL. Hand off to
ds-watch-prif the user asked for watching. gh pr createfails twice. If the error is a GraphQL rate limit, retry once through REST:gh api repos/<owner>/<repo>/pulls -f title=... -f head=... -f base=... -F body=@body.md. If that fails too, report the error.
Rules
- No file-by-file change lists in the description.
- Do not post follow-up comments unless the request needs one. Use
ds-pr-commentswhen it does. - Never guess a model name.
