Ask me what skills you need
What are you building?
Tell me what you're working on and I'll find the best agent skills for you.
PR creation workflow, title format, description template, and quality gates
Apply this rule whenever work touches:
*Pull requests are the primary review mechanism for changes to a published npm package. Every PR must be focused, well-described, and pass all quality gates.
PR titles are human-readable summaries — NOT conventional commit messages. The title should describe what the PR accomplishes at a high level.
GOOD titles:
"Add MassID IPFS and JSON schema definitions"
"Implement shared coordinate validation schema"
"Fix UUID validation edge case for nil values"
"Upgrade Zod to v4 with strict object migration"
BAD titles (conventional commit format):
"feat(schema): add mass-id ipfs schema"
"fix(shared): resolve uuid validation"
"chore: upgrade zod"
Keep titles under 70 characters when possible. Use the description for details.
Aim for focused, reviewable PRs:
When a change exceeds these limits, split it into logical increments:
npx skills add carrot-foundation/schemas --skill rule-pull-requestHow clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
Very clear and well structured, with almost no room for misunderstanding.
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
Highly actionable with clear, concrete steps that an agent can follow directly.