agentleFS
Sign inStart free
aicodekingaicodeking/deepseek-stack/skills/ds-pr/SKILL.md

ds-pr

Skill80 starsChanged 15 days agoMITView on GitHub

Files a short, clear pull request for the current branch. Use when the user asks to open, file or create a PR, or says /ds-pr.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if a PR already exists for this branch (gh pr list --head <branch>).

    line 10
  2. Distinctive:

    Read the titles of a few recently merged PRs and copy their format.

    line 12
  3. Distinctive:

    Write a title that says what changed for the user and why it matters, not which function moved.

    line 13
  4. Distinctive:

    Write the description in this order:

    line 14
  5. Distinctive:

    Create the PR as ready for review, not a draft, so review bots run.

    line 20
  6. Distinctive:

    No file-by-file change lists in the description.

    line 30
  7. Very specific:

    Do not post follow-up comments unless the request needs one.

    line 31
  8. Distinctive:

    Never guess a model name.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 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-comments when it does.
  • Never guess a model name.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free