open-source-maintainer
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.
More from numman-ali/n-skills
gastown
Multi-agent orchestrator for Claude Code. Use when user mentions gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination, beads, hooks, molecules, workflows, the witness, the mayor, the refinery, the deacon, dogs, escalation, or wants to run multiple AI agents on projects simultaneously. Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.
39orchestration
Multi-agent orchestration for complex tasks. Use when tasks require parallel work, multiple agents, or sophisticated coordination. Triggers include requests for features, reviews, refactoring, testing, documentation, or any work that benefits from decomposition into parallel subtasks. This skill defines how to orchestrate work using cc-mirror tasks for persistent dependency tracking and TodoWrite for real-time session visibility.
38zai-cli
|
34dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
25