Help us improve
Share bugs, ideas, or general feedback.
From arn-code
Assesses codebase against stored code patterns for compliance, identifies prioritized improvements via wrapped arn-code-assess skill, performs pre-flight checks, and chains to arn-implementing.
npx claudepluginhub appsvortex/arness --plugin arn-codeHow this skill is triggered — by the user, by Claude, or both
Slash command
/arn-code:arn-assessingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive technical assessment of the codebase against stored patterns, followed by prioritized improvement identification. This is a first-citizen entry point that wraps `arn-code-assess` with a pre-flight check and provides chaining context to `arn-implementing`.
Assesses codebases against Arness patterns in CLAUDE.md, prioritizes improvements via decision gates, and orchestrates multi-spec pipeline from planning and execution to testing and shipping.
Runs codebase audits (health, evaluation, documentation) with parallel agents, producing intake docs for a pipeline run.
Conducts full codebase health audit across architecture, security, code quality, dependencies, test coverage. Produces scored report with letter grades and prioritized remediation. Use for existing codebases or before releases.
Share bugs, ideas, or general feedback.
Comprehensive technical assessment of the codebase against stored patterns, followed by prioritized improvement identification. This is a first-citizen entry point that wraps arn-code-assess with a pre-flight check and provides chaining context to arn-implementing.
This skill is a medium orchestration wrapper. It MUST NOT duplicate arn-code-assess logic. All assessment work is done by the invoked skill (which has its own 7 internal gates). Arness-assessing handles: prerequisite checks, pre-flight validation, invoking the assess skill, and offering the chain exit.
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/ensure-config.md and follow its instructions. This guarantees a user profile exists and ## Arness is configured with Arness Code fields before proceeding.
After Step 0 completes, extract the following from ## Arness:
Verify that pattern documentation exists at the configured Code patterns path:
<code-patterns-dir>/code-patterns.md<code-patterns-dir>/testing-patterns.md<code-patterns-dir>/architecture.mdIf any are missing: inform the user: "Pattern documentation is incomplete. The assessment needs stored patterns to compare against. Run /arn-planning first — it will generate pattern docs on first use." Do not proceed.
If all exist: inform the user briefly: "Pattern documentation found. Starting assessment..."
Show progress:
Assessing: PRE-FLIGHT -> ASSESSMENT (scope -> analyze -> prioritize -> spec -> plan -> execute -> ship -> update-patterns)
^^^^^^^^^^
Invoke the assess skill:
Skill: arn-code:arn-code-assess
The assess skill has its own 7 internal decision gates (scope selection, improvement selection, spec review, execution mode, etc.) and manages its own complete pipeline internally. Wait for it to complete.
After arn-code-assess completes, offer the chain exit:
Ask (using AskUserQuestion):
"Assessment complete. What next?"
Options:
If Implement improvements: Skill: arn-code:arn-implementing
If Done: Exit.
## Arness config missing: Handled by Step 0 (ensure-config) — this should not occur if Step 0 completed successfully./arn-planning which will generate pattern docs on first use.arn-code-assess fails: Present the error. Ask: retry or abort.