issue-to-pr-skills
AGENTS.md0 starsChanged 51 days agoMITView on GitHub
Specialist personas dispatched by Stations II–V based on the diff. A persona missing from disk is skipped and recorded — never simulated. Copy the closest agents/*.md, keep the role narrow (one stack or axis), and make sure at least one station's routing table can reach it. See CONTRIBUTING.md.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/humanizer/AGENTS.mdAGENTS.md
- skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- click-path-auditSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- create-issueSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- diagnosing-bugsSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- extract-design-systemSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- humanizerSkill
- idea-refineSkill
- iiib-iterate-after-buildSkill
- iii-build-planSkill
- ii-plan-issueSkill
- incremental-implementationSkill
- interview-meSkill
- i-pick-issueSkill
- iv-review-build-and-prSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- pipeline-triageSkill
- planning-and-task-breakdownSkill
- playwright-cliSkill
- present-prSkill
- quick-fixSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- tailwind-design-systemSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
- v-babysit-pr-and-mergeSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-completionSkill
- vi-close-pipelineSkill
- web-design-guidelinesSkill
The file
We split this agents.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 10
If agents/<name>.md is missing, that reviewer is skipped — not simulated.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Agents — Reviewer Personas
Specialist personas dispatched by Stations II–V based on the diff. A persona missing from disk is skipped and recorded — never simulated.
Dispatch Rules
- Station II detects stack and writes the reviewer set into
tasks/plan.md. - Station IV fans out to diff-matched reviewers in parallel; the Spec axis runs separately.
- Station V reuses prior review evidence; only new delta is re-reviewed.
- If
agents/<name>.mdis missing, that reviewer is skipped — not simulated.
Catalog
| Agent | Role | Triggers on |
code-reviewer | General quality, five-axis review | every PR |
security-reviewer | OWASP, auth, secrets | auth, input, secrets in diff |
typescript-reviewer | TS/JS types, async, Node | *.ts, *.js |
react-reviewer | Hooks, a11y, RSC, perf | *.tsx, *.jsx |
python-reviewer | asyncio, typing, PEP 8 | *.py |
go-reviewer | goroutines, errors | *.go |
rust-reviewer | lifetimes, unsafe | *.rs |
database-reviewer | SQL/ORM, N+1, indexes | migrations, queries |
silent-failure-hunter | Swallowed errors, lost traces | try/catch, empty handles |
tdd-guide | Write-tests-first | station III per task |
type-design-analyzer | Interface/domain design | API, schema changes |
code-explorer | Path tracing | unfamiliar code |
doc-updater | Docs drift | behavior changes |
build-error-resolver | Generic build failures | build breaks |
react-build-resolver | React build | React build breaks |
go-build-resolver | Go build | Go build breaks |
rust-build-resolver | Rust build | Rust build breaks |
Adding a New Agent
Copy the closest agents/*.md, keep the role narrow (one stack or axis), and make sure at least one station's routing table can reach it. See CONTRIBUTING.md.
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.