naorpeled Maintainer triage and review
Use this skill for ongoing maintainer workflows and targeted repo-health improvements.
Primary inputs
- issue templates
- pull request templates
README.mdCONTRIBUTING.mdDEVELOPER.mdordocs/development.md- labels, governance docs, and repository conventions
AGENTS.md/CLAUDE.mdand output from automated review bots
Instructions
Ongoing workflows
- Triage incoming issues by classifying them as bug, feature, question, docs, or support.
- Request missing reproduction steps, expected behavior, or environment details when needed.
- Review pull requests against the documented contribution and validation rules.
- Check whether contributor-facing docs still match actual repository behavior.
- Weigh findings from automated code review or compliance bots against the actual code before asking a contributor to act on them.
One-off improvements
- Audit whether a newcomer can understand the project from its top-level docs.
- Improve templates or contribution guidance when repeated confusion appears.
- Suggest clearer documentation paths for non-code contributions and beginner issues.
Recommendations to apply
- Treat documentation, labeling, and review clarity as maintainer work, not just code review.
- Encourage beginner-friendly issue labeling where appropriate.
- Surface missing onboarding details that slow down first-time contributors.
- Give specific, actionable feedback in a friendly tone, and invite the contributor's input on open design questions rather than dictating them.
Output format
Return one or more of:
- triage notes and follow-up questions
- review feedback grounded in repo conventions
- documentation drift findings
- a short list of maintainer improvements