mcpField
D
ds-pr

ds-pr

github.com/aicodekingDevelopment150268 installsUpdated 6d ago
Repository

About ds-pr

ds-pr is a skill for creating or updating GitHub Pull Requests, aimed at developers who need a clear handoff for a change. It specifies the title and description structure and calls for checks of the diff, sensitive data, and PR status.

Key features

  1. 01Check for an existing branch PR and update it
  2. 02Verify change scope against the base branch
  3. 03Follow title formats from recently merged PRs
  4. 04Structure descriptions around problem, fix, and proof
  5. 05Scan for sensitive data and create a review-ready PR

Use cases

  1. 01Create a PR for the current branch that is quick to review
  2. 02Update an existing PR to reflect current changes
  3. 03Check PR text and attachments for sensitive data before submission

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr

After installing, type/ds-prin Claude Code to confirm it loaded.

Details

From the project README

Open one real PR whose title and description a busy reviewer can read in ten seconds.

Steps

  1. Check if a PR already exists for this branch (gh pr list --head <branch>). If it does, update it.
  2. Diff the branch against its base, usually origin/main. Confirm the diff matches the goal and holds nothing unrelated.
  3. Read the titles of a few recently merged PRs and copy their format.
  4. 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".
  5. 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.
  6. Scan the title, body and any attachments for secrets, tokens, private paths and personal data. Remove them.
  7. Create the PR as ready for review, not a draft, so review bots run.
  8. Print the PR URL that GitHub returned.

Stop when

  • GitHub returned a PR URL. Hand off to ds-watch-pr if the user asked for watching.
  • gh pr create fails 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 [email protected]. 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-comments when it does.
  • Never guess a model name.

Comments

Markdown supported