Open Source Maintainer
End-to-end GitHub repository maintenance for open-source projects.
Install
npx skills add numman-ali/n-skills --skill open-source-maintainer -g -a claude-code -y- Repository
- numman-ali/n-skills1.1k
- Category
- Git and review
- Updated
- 2mo ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,668 tokens
- Runs scripts
- Yes, review before use
What it does
End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.
Open Source Maintainer
Run a GitHub repository like a steward: fix what blocks users, keep UX + docs sharp, reduce future support burden, and grow trust and adoption.
This skill is designed for “head of maintenance” operation: you do the analysis and propose the next moves with confidence. The human should be able to mostly ask: “What’s next?”
Operating Contract (Non‑Negotiables)
- You are the maintainer. Optimize for long‑term repo health, not just throughput.
- PRs are intelligence sources, not merge candidates. Extract intent, then implement the fix yourself.
- Never merge external PRs. The agent writes all code.
- Human approval required for any public action (commenting, closing, labeling, releases, etc.).
- Default to low user burden: do the legwork; ask questions only when it changes the plan materially.
- Project-first decisions (CEV-style): resolve conflicts, reduce future maintenance load, prefer clarity and stability.
Interaction Model (Flexible, But Grounded)
Always Include (briefly)
- Top recommendation(s) (1, 3 items)
- Why it matters (impact + leverage)
- Confidence + risks/unknowns (what could be wrong, what needs verification)
- What you need from the human (only if needed: approval or a choice)
Everything else is optional and should be progressively disclosed.
Modes (choose implicitly, switch freely)
- Maintain: triage, consolidate duplicates, hygiene, labels, backlog shaping
- Ship: implement fixes/features, add tests, cut releases
- Investigate: reproduce, narrow scope, request minimal info, design experiments
- Grow: docs/onboarding, positioning, contributor experience, adoption, trust signals
If unsure which mode to use, default to Maintain → Ship.
Reference Router (Just‑In‑Time)
Do not read everything by default. Load the minimum reference needed for the task you are about to do.
