vibe-maintainer
A set of guidelines for solo maintainers using AI to manage high-velocity open-source PRs and community contributions.
Install
mkdir -p .claude/skills/vibe-maintainer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17410" && unzip -o skill.zip -d .claude/skills/vibe-maintainer && rm skill.zipInstalls to .claude/skills/vibe-maintainer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Maintainer playbook for agent-era OSS — PR triage, fix-merge discipline, and attribution rules for a solo human + AI maintainer.Key capabilities
- →Absorb contributions by default, rejecting only on principle
- →Preserve attribution for original contributors
- →Optimize for throughput rather than per-PR perfection
- →Triage incoming PRs into easy win, fix-merge, or deeper look categories
- →Apply surgical fixes to PRs and merge with attribution
- →Enforce hygiene rules on contributors
How it works
The skill triages incoming pull requests into categories, then applies a decision tree to either merge, fix-merge, cherry-pick, or redesign. It prioritizes absorbing contributions while preserving attribution and optimizing for throughput.
Inputs & outputs
When to use vibe-maintainer
- →Triage incoming community PRs
- →Automate PR labels and attribution
- →Maintain project velocity with AI support
About vibe-maintainer
Defines strategies for absorbing contributions, maintaining authorship attribution, and optimizing for throughput in an agent-assisted environment.
Maintainer playbook for agent-era OSS — PR triage, fix-merge discipline, and attribution rules for a solo human + AI maintainer.
When not to use it
- →Workflows that assume a review committee
Limitations
- →Assumes a solo human + AI maintainer model
- →Does not design workflows that assume a review committee
- →Requires manual re-reading of diffs despite automation output
How it compares
This playbook defines a specific, agent-assisted workflow for maintaining open-source projects with a single human maintainer, emphasizing attribution and throughput over traditional multi-reviewer models.
Compared to similar skills
vibe-maintainer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vibe-maintainer (this skill) | 0 | 3mo | Review | Advanced |
| gh-issue-triage | 1 | 7mo | Review | Intermediate |
| file-todos | 0 | 4mo | Review | Beginner |
| issue-triage-workflow | 0 | 5mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
gh-issue-triage
joelhooks
GitHub issue triage workflow with contributor profile extraction. Analyze → clarify → file cells → tag → implement → credit. Captures Twitter handles for changeset acknowledgments.
file-todos
JimmyChen-NXP
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
issue-triage-workflow
Hack23
Triage GitHub issues: labeling, prioritization, assignment, and resolution tracking
retro
Thawatchai-Petkaew
Run a story retrospective that distills lessons from closed work and feeds them back into the team's memory — appends to the `docs/delivery/LESSONS.md` ledger and proposes promotions into `.claude/rules/<role>.md` for owner approval. Use when a story is Done (merged + verified) and you want the Scou
team-workflow
jevonsnotes
>
drift-analysis
avifenesh
This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.