pr-create
PR Create
Hard rules
These override anything else. No exceptions without an explicit user instruction.
- Never append Claude attribution trailers. No
🤖 Generated with Claude Code, noCo-Authored-By: Claude …, no "Generated by" footers. The PR title and body contain nothing that identifies the author as an AI. - Never force-push unless the user explicitly asks this turn — and only
--force-with-lease, never plain--force. Confirm the head branch is notmain/masterbefore the push. - Never open a PR from
main/master. Stop and surface to the user. - Never auto-rebase or auto-merge the base branch. If the branch is behind, surface it and ask.
- Never fill a checklist item you haven't verified. Leave
[ ]unchecked; don't tick boxes on the user's behalf. - Never open a PR that contains secrets. If the diff touches
.env*,*credentials*,*.pem,*.key, orid_rsa*, stop and surface to the user — even if the user asked you to proceed. Public PRs cache forever.
Workflow
More from robdefeo/agent-skills
amazon-working-backwards
Guide the Amazon Working Backwards process from the 5 Questions through to a full PR-FAQ document. Use when the user wants to (1) draft answers to the Amazon 5 Questions for a proposal or idea, (2) refine or critique existing 5Q answers, (3) verify and challenge 5Q answers with probing questions, (4) generate a PR-FAQ document from 5Q answers, (5) review or critique an existing PR-FAQ against Amazon standards, or (6) clarify any element of the 5Q or PR-FAQ process. Triggers include mentions of "5 questions," "PR-FAQ," "PRFAQ," "working backwards," "press release FAQ," Amazon-style proposals, or requests to write/review product proposals in Amazon format.
476para-second-brain
Use this skill when the user wants to organize, classify, or maintain a PARA-method second brain. Triggers include asking where to file something, distinguishing projects from areas, processing an inbox, setting up a new project, completing or archiving a project, running a monthly review, validating system structure, or finding stale/orphaned content.
322diataxis-documentation-guidance
Use this skill to classify, scope, split, draft, and review documentation with the Diataxis framework. Triggers include choosing tutorial/how-to/reference/explanation mode, resolving mixed-mode pages, rewriting docs into a target mode, and validating drafts with a checklist.
9pr-address-feedback
Use this skill whenever the user wants to address, respond to, work through, or handle GitHub PR review comments — including code review feedback, reviewer suggestions, bot comments, or requested changes — even if they don't say \"address\". Handles the full end-to-end workflow: fetch threads, plan fixes, commit, push, and reply. Requires `gh` CLI.
4