Harness Engineering plugin
A Claude Code plugin with /readiness and /setup skills that scores a repo for agent work and installs rules, hooks and checks.
- 126 ★ on the repository
- Last commit
Extended access
Why this level
- The /setup skill creates and changes project files, git hooks and Claude Code settings.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/harness-engineeringDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The /setup skill creates and changes project files, git hooks and Claude Code settings.
This is third-party code. Review the repository files before installing.
What it does
A Claude Code plugin and reference guide on harness engineering for long-running coding agent sessions. The `/readiness` skill scores any repository across eight pillars and five maturity levels and saves a `readiness-report.md` for tracking over time. The `/setup` skill asks questions to determine the stack, then creates `CLAUDE.md` files, path-scoped rules, check scripts, git hooks and `.claude/settings.json` with safe permission defaults. The scripts catch secrets in code, oversized files, missing colocated tests and documentation drift. A separate `documentation` plugin maintains document indexes and metadata and installs on its own. The reference part maps more than twenty practices from OpenAI, Augment Code, Anthropic and individual engineers to concrete patterns.
Who it is for. Teams and developers who want a repository in which an agent follows project rules across long sessions.
Good fit when
- You want to assess how ready an existing project is for agents and get a list of first fixes.
- A new repository is set up with `CLAUDE.md`, rules, git hooks and safe permissions from day one.
- An agent ignores `CLAUDE.md` instructions and you want hooks and linters to back them.
- Documentation drifts from code and you need automatic indexes and drift checks.
Not a fit when
- The work does not happen in Claude Code, while the plugin relies on its skills, hooks and settings.
- The repository is shared and you may not change its hooks or `CLAUDE.md`.
- A short `CLAUDE.md` of a few lines is enough and a separate check infrastructure is overkill.
Example request
How ready is my project for agents? Run an assessment and show what to fix first.Limitations
The plugin targets Claude Code with plugin support and Git. Scripts and hooks rely on Node.js 18 or newer: for Python, Go and Rust projects Node remains the runtime for documentation tooling. The `/setup` skill changes the repository by writing `CLAUDE.md`, scripts, hooks and settings, and the hooks block commits and pushes on rule violations, so run it on a separate branch and review the diff. By description it preserves existing prose, hooks and settings and never stages files automatically, but verification stays with you. The readiness score reflects repository structure and does not replace code review.
How to disable. Run `/plugin uninstall harness-engineering@harness-engineering`. Remove files, hooks and settings created by `/setup` from the repository by hand.
FAQ
How do I install Harness Engineering in Claude Code?
Run `/plugin marketplace add jrenaldi79/harness-engineering`, then `/plugin install harness-engineering@harness-engineering`. After that you can ask in plain words or call `/readiness` and `/setup`.
What does /readiness score?
Eight readiness pillars and five maturity levels. The report is saved to `readiness-report.md` so results can be compared over time.
Can I install only the documentation part?
Yes. The `documentation` plugin installs separately: `/plugin install documentation@harness-engineering`, then `/documentation:documentation`.
Does the plugin work for non-Node projects?
Yes. `/setup` adapts to Python, Go, Rust and C/C++, while Node/TypeScript remains the recommended default for web projects.
What does /setup do?
It asks questions to determine the stack, then creates `CLAUDE.md`, path-scoped rules, check scripts, git hooks and `.claude/settings.json` with safe permissions.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin that generates and maintains CLAUDE.md: a 0 to 100 quality score, a 150-line cap and stale reference checks
A CLI, hooks and skills for long Claude, Codex and Pi work: the issue and PR own the task and review gets a PR with checks
Codely team skills that run agent work in phases: a plan in a file or GitHub issues, review after each phase and a clean commit
A Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
Ready infrastructure for Claude Code: skill auto-activation via hooks, a skill set, agents, slash commands and a wizard that installs it into your project
README in short
Covers plugin installation, the three-step flow, the mapping to industry practices, how rules and hooks work and quality gates.