By zeyuzhangzyz
Automate end-to-end open-source repository hardening: audit gaps in correctness, security, maintainability, tests, docs, and CI; generate plans and checklists; apply minimal refactors; add tests, GitHub Actions workflows, and docs; run iterative senior reviews until release-ready.
Audit an existing repository or paper-code release for open-source hardening gaps across correctness, maintainability, testability, security, performance, observability, and documentation. Use when the user says "audit this repo", "harden this project", "open source readiness", or wants a prioritized file-level report before changing code.
Add or improve a minimal GitHub Actions CI pipeline for linting and tests. Use when the user says "set up CI", "add GitHub Actions", "block bad PRs", or wants a cache-enabled pull-request workflow that runs without secrets.
Improve the repository's open-source documentation and metadata. Use when the user says "improve docs", "make this repo easier to adopt", "fix the README", or wants README polish plus SECURITY.md, CHANGELOG.md, FAQ, architecture notes, and paper-release metadata.
Orchestrate an end-to-end open-source hardening pass for a repository. Use when the user wants to turn a loose codebase or paper-code release into a readable, testable, maintainable open-source project and wants audit, plan, refactor, tests, CI, and docs to run as one continuous workflow unless a blocker appears.
Convert an open-source hardening audit into an executable implementation plan. Use when the user says "turn this audit into a plan", "make a checklist", "write a GitHub issue", or wants a PR-ready checklist with acceptance criteria and commands for a software repo or paper-code release.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
English | 中文
Open Source Hardening Skills is a skill pack for ARIS / Claude Code that hardens any repository - app, library, CLI tool, or research paper codebase - into a readable, testable, maintainable open-source project.
Pairs naturally with ARIS. ARIS (v0.3+) is a multi-IDE autonomous research ecosystem with 31+ skills supporting Claude Code, Codex CLI, Cursor, Trae, and more. Open Source Hardening Skills is the next step that gets the resulting code ready for public release.
[ARIS research pipeline] [Open Source Hardening Skills pipeline]
/idea-discovery /oss-audit -> scan for gaps
/auto-review-loop ------> /oss-plan -> make a checklist
/paper-writing /oss-refactor -> minimal cleanup
(code exists) /oss-tests -> add CI-safe tests
/oss-ci -> block bad PRs
/oss-docs -> polish docs
/oss-review-loop -> external quality gate
(repo is release-ready)
Open Source Hardening Skills also works standalone on any existing repository - no ARIS required.
| Skill | Trigger | What it does |
|---|---|---|
| oss-audit | /oss-audit | Scans 7 dimensions, outputs a prioritized file-level report (OSS_AUDIT.md) |
| oss-plan | /oss-plan | Converts audit findings into a PR-ready checklist (OSS_PLAN.md) |
| oss-refactor | /oss-refactor | Applies the smallest structural changes needed to unlock tests and CI |
| oss-tests | /oss-tests | Builds a minimal automated test loop that runs without secrets |
| oss-ci | /oss-ci | Adds or improves a GitHub Actions pipeline that blocks broken PRs |
| oss-docs | /oss-docs | Polishes README, adds SECURITY.md, CHANGELOG.md, and contribution guidance |
| oss-review | /oss-review | One-shot external review via Codex MCP (GPT-5.4) |
| oss-review-loop | /oss-review-loop | Iterative review -> fix -> re-review until release-ready (max 4 rounds) |
| oss-hardening | /oss-hardening | Orchestrates the full pipeline end-to-end in one command |
| oss-search | /oss-search | Searches GitHub and the web for reference repos, CI examples, and best practices - no API keys required |
Install Claude Code first, then open it once to finish login and create ~/.claude/:
# macOS / Linux / WSL
curl -fsSL https://claude.ai/install.sh | bash
# Windows PowerShell
irm https://claude.ai/install.ps1 | iex
cd your-project
claude
macOS / Linux / WSL (one-liner):
curl -fsSL https://raw.githubusercontent.com/zeyuzhangzyz/open-source-hardening-skills/main/install.sh | bash
Or clone and run manually:
git clone https://github.com/zeyuzhangzyz/open-source-hardening-skills.git
cd open-source-hardening-skills
bash install.sh
Windows PowerShell (one-liner):
irm https://raw.githubusercontent.com/zeyuzhangzyz/open-source-hardening-skills/main/install.ps1 | iex
Or clone and run manually:
git clone https://github.com/zeyuzhangzyz/open-source-hardening-skills.git
cd open-source-hardening-skills
.\install.ps1
The install scripts are idempotent: re-running them updates the skills to the latest version. They only replace this pack's own oss-* skill directories and never touch other skills you may have installed.
/oss-review and /oss-review-loop call the external reviewer via the official Codex MCP tools (mcp__codex__codex, mcp__codex__codex-reply). The other 8 skills work without it.
npm install -g @openai/codex
codex setup # set model to gpt-5.4 when prompted
claude mcp add codex -s user -- codex mcp-server
Tip: ARIS v0.3+ also ships alternative review bridges (Claude, Gemini, any OpenAI-compatible API). If you already have one configured,
/oss-reviewwill use whichever Codex MCP endpoint is available.
/oss-hardening .
After a full run, the pipeline generates these artifacts in your repo root:
OSS_AUDIT.md <- gap analysis across 7 dimensions
OSS_PLAN.md <- PR-ready checklist with acceptance criteria
OSS_REFACTOR.md <- summary of structural changes applied
OSS_TEST_STRATEGY.md <- test framework, commands, and mock strategy
OSS_CI.md <- CI workflow documentation
OSS_DOCS.md <- documentation improvement checklist
OSS_REVIEW_LOOP.md <- iterative review log with scores per round
OSS_HARDENING_STATUS.md <- final verdict, score, and next steps
npx claudepluginhub zeyuzhangzyz/open-source-hardening-skillsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses