codex-oss-maintainer-toolkit
- Repo stars 0
- Author repo skills-registry
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
scripts/init_skill.pyfor reusable task playbooks. - Put durable procedures in
references/. - Put deterministic checks in
templates/automation/or project scripts.
- 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
references/workflows.md: multi-step maintainer workflow patternsreferences/output-patterns.md: structured output formats for triage, review, and release communicationtemplates/AGENTS.md: project bootstrap templatetemplates/automation/README.md: helper script usage
Validation Checklist
-
AGENTS.mdmatches the repository layout - public docs use Codex/OpenAI terminology consistently
- skills are concise and validated
- automation scripts have explicit inputs and outputs
- examples and templates stay synchronized
<!-- tomevault:4.0:skill_md:2026-05-23 -->Source: ComeOnOliver/skillshub — distributed by TomeVault.
- Fluxly category
- Productivity
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @tomevault-io · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Plug-and-play
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. Quick Start
Audit the repository Identify maintainer bottlenecks: issue triage, review latency, release friction, repeated debugging. Map the folders that need project-specific instructions.
Maintainer Workflow Patterns
# Codex OSS Maintainer Toolkit
Use this skill to turn an open-source repository into a Codex-friendly maintainer workspace.
## Quick Start
```bash
./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
1. **Audit the repository**
- Identify maintainer bottlenecks: issue triage, review latency, release friction, repeated debugging.
- Map the folders that need project-specific instructions.
2. **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.
3. **Move repeatable tasks into skills or scripts**
- Use `scripts/init_skill.py` for reusable task playbooks.
- Put durable procedures in `references/`.
- Put deterministic checks in `templates/automation/` or project scripts.
4. **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.
5. **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
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Quick Start → What This Skill Optimizes → Recommended Workflow → Maintainer Workflow Patterns → Issue Triage → PR Review
terms -> Audit the repository · Write AGENTS.md close to the work · Move repeatable tasks into skills or scripts · Design for maintainers, not demos · Validate before shipping
files/cmd -> AGENTS.md · scripts/initskill.py · references/ · templates/automation/ · references/workflows.md · references/output-patterns.md · templates/AGENTS.md · templates/automation/README.md
body sha256 -> f2de5528f66f
Decide Fit First
Design Intent
How To Use It
Boundaries And Review