Loading...
Loading...
Found 19 Skills
When reporting that work is completed, fixed, or ready for use before submitting or creating a PR - you need to run verification commands and confirm the output before making any success claims; evidence always precedes assertion
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
Polish code changes by recovering context, checking against codebase guidelines, removing AI slop, and running review. Use when finalizing work on a branch before PR.
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when the user wants to clean up messy commits, create a tutorial-style commit history, or prepare a branch for review with logical, self-contained commits. Triggers on requests like "clean up my commits", "reimplement this branch", "create a clean history", or "make my commits reviewable".
Contribute changes to the Feynman repository itself. Use when the task is to add features, fix bugs, update prompts or skills, change install or release behavior, improve docs, or prepare a focused PR against this repo.
Reviews the current local diff or branch at the end of a coding session for high-confidence bugs and repository instruction-file compliance. Use when asked to run `/pr-reviewer` before commit, before push, or before handing changes off for PR creation or update, and when only certain, actionable findings should be reported while style feedback is ignored.