install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/IndianOldTurtledove/codex-oss-maintainer-toolkit/codex-oss-maintainer-toolkit" ~/.claude/skills/comeonoliver-skillshub-codex-oss-maintainer-toolkit-af40ac && rm -rf "$T"
manifest:
skills/IndianOldTurtledove/codex-oss-maintainer-toolkit/codex-oss-maintainer-toolkit/SKILL.mdsource content
Codex OSS Maintainer Toolkit
Use this skill to turn an open-source repository into a Codex-friendly maintainer workspace.
Quick Start
./install.sh --project --target /path/to/repo --yes ./install.sh --global --yes python3 scripts/init_skill.py issue-triage python3 scripts/quick_validate.py .codex/skills/issue-triage
What This Skill Optimizes
- project-level
AGENTS.md - maintainer-focused Codex skills
- issue triage and bug-investigation workflows
- PR review and release-note prompts
- reusable verification commands
- cross-session dev docs for long-running tasks
Recommended Workflow
-
Audit the repository
- Identify maintainer bottlenecks: issue triage, review latency, release friction, repeated debugging.
- Map the folders that need project-specific instructions.
-
Write AGENTS.md close to the work
- Keep global instructions short.
- Add repo-specific rules, validation commands, and ownership notes.
- Prefer operational guidance over abstract philosophy.
-
Move repeatable tasks into skills or scripts
- Use
for reusable task playbooks.scripts/init_skill.py - Put durable procedures in
.references/ - Put deterministic checks in
or project scripts.templates/automation/
- Use
-
Design for maintainers, not demos
- Prioritize issue triage, review, release, dependency updates, and regression checks.
- Keep verification commands next to the workflow that needs them.
-
Validate before shipping
- Run targeted checks.
- Search for stale branding or paths.
- Keep templates and examples in sync.
Maintainer Workflow Patterns
Issue Triage
- summarize the report
- classify bug vs feature vs support request
- link affected paths and owners
- propose the next maintainer action
PR Review
- inspect diff boundaries first
- check architecture, tests, rollback risk, and release notes
- produce actionable comments instead of generic praise
Debugging
- reproduce first
- inspect the failing path before editing
- test one hypothesis at a time
- verify both the fix and the absence of regressions
Release Notes
- group changes by user-facing impact
- capture migrations, flags, or rollout constraints
- link verification commands and rollback notes
Files to Read When Needed
: multi-step maintainer workflow patternsreferences/workflows.md
: structured output formats for triage, review, and release communicationreferences/output-patterns.md
: project bootstrap templatetemplates/AGENTS.md
: helper script usagetemplates/automation/README.md
Validation Checklist
-
matches the repository layoutAGENTS.md - public docs use Codex/OpenAI terminology consistently
- skills are concise and validated
- automation scripts have explicit inputs and outputs
- examples and templates stay synchronized