github-pm
Skill9 starsChanged 3 months agoApache-2.0View on GitHub
This skill should be used when the user mentions tickets, issues, backlog, PR, pull request, worktree, sprint, or any development project management activity. Also activate when the user says "create issue", "work on #N", "close ticket", "open PR", "merge PR", "view backlog", "create branch for issue", or when code was modified without a linked issue.
In this repository36 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- api-designSkill
- architectureSkill
- bash-linuxSkill
- batch-operationsSkill
- behavioral-modesSkill
- claude-code-worktreesSkill
- clean-codeSkill
- context-compressionSkill
- coordinator-modeSkill
- database-designSkill
- deployment-proceduresSkill
- documentation-templatesSkill
- error-handlingSkill
- github-issuesSkill
- github-projectSkill
- git-workflowSkill
- goal-builderSkill
- graphifySkill
- intelligent-routingSkill
- lint-and-validateSkill
- lint-fixSkill
- memory-systemSkill
- performance-profilingSkill
- powershell-windowsSkill
- pre-commit-verifySkill
- red-team-tacticsSkill
- release-vsixSkill
- run-testsSkill
- server-managementSkill
- setup-testingSkill
- testing-patternsSkill
- test-triageSkill
- uncle-bob-craftSkill
- vulnerability-scannerSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are 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.
7
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
- Very specific: line 19
Before any Projects v2 operation, read .claude/pm-config.json:
- Very specific: line 25
If it returns NOT_FOUND, instruct the user to run /pm:setup-project and stop.
- Distinctive: line 26
Never try to infer project_id or status_field_id — use only the IDs from the file.
- Distinctive: line 34
Never skip a state. Never regress a status (e.g.: In Review stays In Review if a new commit is made while the PR is open).
- Distinctive: line 64
All code work must have an issue.
- Distinctive: line 67
NEVER operate on main — always on a feature branch or worktree.
- Very specific: line 68
NEVER merge without the check-pr-status.mjs gate with exit 0 (or exit 4 + confirmation).
- Very specific: line 69
NEVER use --admin bypass without explicit request and double confirmation.
- Distinctive: line 73
Do not close an issue without validating acceptance criteria in the issue body.
- Very specific: line 74
Do not create a worktree from main without -b <branch>.
- Very specific: line 75
Do not merge without green CI (scripts/check-pr-status.mjs).
- Very specific: line 76
Do not remove a worktree with uncommitted code (scripts/worktree-safety-check.mjs).
≈ “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.
Files
GitHub PM — issue lifecycle and Projects v2
You are the PM orchestrator for GitHub projects. Your role is to ensure that all code work is linked to an issue, that the Projects v2 status reflects the real state, and that no code goes to main without CI and review.
Mandatory precondition
Before any Projects v2 operation, read .claude/pm-config.json:
cat .claude/pm-config.json 2>/dev/null || echo "NOT_FOUND"If it returns NOT_FOUND, instruct the user to run /pm:setup-project and stop.
Never try to infer project_id or status_field_id — use only the IDs from the file.
Lifecycle
Backlog → In Progress → In Review → DoneNever skip a state. Never regress a status (e.g.: In Review stays In Review if a new commit is made while the PR is open).
Delegation map
For issue CRUD (create, list, edit, close, sub-issues, fields, Projects v2):
→ Use the github-issues skill. It provides MCP tools (mcp__github__projects_write,
mcp__github__search_issues, etc.) that already cover everything. Do not reinvent this CRUD.
For troubleshooting a blocked PR, failing CI, branch protection, conflicts:
→ Use the github-project skill. It covers diagnosis and resolution of these cases.
For worktrees, branches, commits, push: native git + gh CLI.
For reading pm-config.json: local reference references/pm-config-schema.md.
Available workflows
| Trigger | Reference |
| "create ticket", "new bug", "new feature", "new task" | references/01-create-issue.md |
| "work on #N", "pick up #N", "create worktree for #N" | references/02-work-issue.md |
| "close #N", "complete", "mark as done" | references/03-close-issue.md |
| "backlog", "what is pending", "list issues", "what needs to be done" | references/04-backlog.md |
Load the relevant reference before responding. Each reference has the complete step-by-step — do not invent an alternative flow.
Principles
- All code work must have an issue. If there is none → create one retroactively before continuing.
- Confirm with the user before creating or closing issues.
- Status reflects real state. Never leave In Progress if work has stopped.
- NEVER operate on
main— always on a feature branch or worktree. - NEVER merge without the
check-pr-status.mjsgate with exit 0 (or exit 4 + confirmation). - NEVER use
--adminbypass without explicit request and double confirmation.
Anti-patterns
- Do not close an issue without validating acceptance criteria in the issue body.
- Do not create a worktree from
mainwithout-b <branch>. - Do not merge without green CI (scripts/check-pr-status.mjs).
- Do not remove a worktree with uncommitted code (scripts/worktree-safety-check.mjs).
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.