All authors
Claude Skills by pantstamp
github.com/pantstamp6 skills0 installs0 views
- ArchitectDesigns a feature together with the user and turns the approved SPEC.md into a phased PLAN.md that another agent can execute without further context: briefs the user on the code the feature touches with a current-state diagram, has the user propose their own design first, reviews it honestly against best practice and the codebase, then writes buildable, dependency-ordered phases with files, signatures, tests and a verification command each. Use when the user wants an implementation plan, a te...Votes: 0GitHub stars: 15
- DeveloperImplements a PLAN.md one phase at a time on the feature branch, running each phase's verification, committing it, and stopping for the user's approval before the next; then offers the pre-PR gate, and pushes and opens the pull request. Use when the user wants to implement, build or execute a plan, start or resume a phase, or create the PR.Votes: 0GitHub stars: 15
- Pre Pr ChecklistRuns a pre-PR quality gate on a feature branch: checks that the PLAN.md was followed, that each SPEC.md acceptance criterion is covered, that no debug leftovers or TODOs are in the diff, and that the changed code follows the project's written judgement rules, then runs a local mirror of CI and reports GO, CONDITIONAL GO or NO GO. Use when the user asks whether a branch is ready for a PR, or for a pre-PR check, quality gate or final check.Votes: 0GitHub stars: 15
- Product OwnerInterviews the user one topic at a time to turn raw requirements or an issue into a SPEC.md with user stories, acceptance criteria, edge cases and out-of-scope items, on a new feature or fix branch. Use when the user wants to spec, scope or define a feature or bug fix, write user stories or acceptance criteria, or start work on an issue.Votes: 0GitHub stars: 15
- RetrospectiveRuns a post-merge retrospective for a feature's pull request: reads the review comments, the diff, the fix commits, SPEC.md and PLAN.md, writes a RETRO.md comparing against earlier retros, and routes each lesson to the project's rules, an architecture or lint rule, a skill, or the review prompt. Use after a PR is merged when the user asks for a retro, retrospective, lessons learned, or to turn review findings into project rules.Votes: 0GitHub stars: 15
- Review TriageWalks through a pull request's inline review comments one at a time, showing the code, the suggestion and an assessment, and waits for the user's decision on each; then applies the accepted fixes, verifies, commits, pushes, replies on each thread, and checks for comments newer than the last commit before merge. Use when the user wants to triage, go through or address PR review comments or findings.Votes: 0GitHub stars: 15