From open-source-hardening-skills
Orchestrates end-to-end OSS hardening pipeline (audit, plan, refactor, tests, CI, docs, review) continuously on repositories, pausing only on blockers. For loose codebases or paper releases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/open-source-hardening-skills:oss-hardeningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a staged hardening pipeline in one continuous pass by default:
Run a staged hardening pipeline in one continuous pass by default:
/oss-audit/oss-plan/oss-refactor/oss-tests/oss-ci/oss-docs/oss-review-loopDefault behavior:
audit -> plan -> refactor -> tests -> ci -> docs -> review-loop in one invocationDo not force the user to manually re-issue every stage command unless they explicitly ask for stage-by-stage control.
Create or update OSS_HARDENING_STATUS.md with:
If the workflow pauses, give the user a short "where we are / what comes next" summary. If the workflow finishes continuously, give one end-to-end summary plus any blockers left deferred.
Run /oss-audit first, then continue directly to /oss-plan if no blocker is found.
Stop here if:
Run /oss-plan once the audit has concrete P0/P1/P2 findings, then continue directly to /oss-refactor when the plan is actionable.
Stop here if:
Run /oss-refactor only for the smallest structural changes needed to unlock tests and CI, then continue directly to /oss-tests when behavior remains stable.
Rollback or pause if:
Run /oss-tests after the structure is stable enough to test, then continue directly to /oss-ci when the local test command is trustworthy.
Stop here if:
Run /oss-ci only after local lint and test commands are trustworthy, then continue directly to /oss-docs once CI reflects the intended local workflow.
Rollback or pause if:
Run /oss-docs so the documentation reflects the final behavior and commands, then continue directly to /oss-review-loop if all prior stages passed cleanly.
Stop here if:
Run /oss-review-loop after docs so the pipeline ends with an external Codex quality gate and up to four rounds of iterative fixes. The review loop uses the official mcp__codex__codex / mcp__codex__codex-reply tools as its primary entry point.
If the loop returns:
ready: finish the hardening passalmost: either stop with explicit remaining gaps or do one targeted follow-up pass and rerun reviewnot ready: return to the highest-leverage recommended stage (audit, plan, refactor, tests, ci, or docs)/oss-review remains useful as a one-shot checkpoint when the user wants a single external pass without the full loop.
OSS_HARDENING_STATUS.md.Before declaring this stage complete, verify:
OSS_HARDENING_STATUS.md exists and lists current stage, completed artifacts, execution mode, unresolved maintainer decisions, next command, and stop/rollback conditions./oss-audit or /oss-plan and record why./oss-review-loop fails the repo after max rounds, record the recommended return stage and do not claim the pipeline is complete.OSS_HARDENING_STATUS.md exists and records current stage, completed artifacts, execution mode, unresolved decisions, next command, and stop/rollback conditions.npx claudepluginhub zeyuzhangzyz/open-source-hardening-skills3-agent pipeline (forker, sanitizer, packager) that forks private repos, strips secrets, verifies cleanliness, and generates CLAUDE.md, setup.sh, and README for safe public release.
Audits open source repo health, scaffolds LICENSE/CODE_OF_CONDUCT/CONTRIBUTING/SECURITY files, sets up GitHub issue/PR templates, Actions for labeling/stale/welcome/release, and governance docs. Use for new OSS projects or publishing repos.
Executes 7-stage workflow to audit GitHub repos for secrets, junk files, broken links; cleans up, reviews PRs, benchmarks competitors, and validates fixes. Ideal for repo optimization and competitor analysis.