使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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.
