pr-per-story
Skill0 starsChanged 37 days agoMITView on GitHub
Finish a feature by running the spec's verification command, iterating on failures, and opening a pull request whose description is generated from the spec. Use when implementation work is complete and ready for review, the user says the feature is done or asks for a PR. Never merges.
- Commits and pushes
In this repository2 other files it gives its agents.
- spec-firstSkill
- worktree-storySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Every feature ends in a pull request: a bounded diff, traceable to its spec, merged by a human.
- Very specific: line 68
A PR already exists for this branch: update it (push, gh pr edit) instead of opening a duplicate.
- Distinctive: line 73
Never merge, enable auto-merge, approve your own PR, or delete the branch.
- Distinctive: line 74
Never check an acceptance-criteria box you did not verify in this session.
- Distinctive: line 75
Never weaken, skip, or delete a failing test to make verification pass.
- Distinctive: line 76
Never force-push over commits you did not create.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
PR Per Feature (User Story): Verified Diff, Human Merge
Every feature ends in a pull request: a bounded diff, traceable to its spec, merged by a human. This skill closes the loop.
Workflow
- Re-read the spec (
specs/<slug>.md). The PR is judged against the spec, not against the chat history. If no spec exists, write down the acceptance criteria you are about to claim and confirm them with the user first. - Run the spec's verification command exactly as written, then walk the acceptance criteria one by one.
- Iterate on failures, best effort, honestly reported. Fix, re-run, repeat. If it still fails after a handful of focused attempts, or the fix would change the spec's scope, stop and report exactly what fails and why. A red check reported honestly beats a green check achieved by weakening the test.
- Review your own diff before pushing:
git diff <base>...HEAD --stat, then the full diff. Remove debug output, stray files, and unrelated reformatting. Everything left in the diff must trace back to the spec. Push the feature branch and open the PR (from the feature worktree, see the worktree-story skill):
git push -u origin feature/<slug> gh pr create --title "<feature title>" --body-file <body file>Generate the PR description FROM the spec, in this shape:
## What One paragraph, the change, taken from the spec's Scope. ## Why Taken from the spec's Context. ## Acceptance criteria - [x] Each criterion from the spec, checked only if verified in this session - [ ] Unmet criteria stay unchecked, with a one-line note ## Test evidence The verification command and a summary of its real output (pass/fail counts, not just "tests pass"). Spec: specs/<slug>.md- Stop. Post the PR URL and the verification summary, then hand off. Merging is the human's decision, always.
Edge cases
- No remote or no
ghCLI: push the branch and print the compare URL, or output the PR title and body as text the user can paste. - Verification command itself is broken (fails before testing anything): fixing the harness is in scope only if the spec says so, otherwise report it and stop.
- Out-of-scope changes crept into the diff: split them out before opening the PR, even if they are improvements.
- A PR already exists for this branch: update it (push,
gh pr edit) instead of opening a duplicate.
Boundaries
- Never merge, enable auto-merge, approve your own PR, or delete the branch.
- Never check an acceptance-criteria box you did not verify in this session.
- Never weaken, skip, or delete a failing test to make verification pass.
- Never force-push over commits you did not create.
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
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.

