From arn-code
This skill should be used when the user says "assessing", "arness assessing", "assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "pattern compliance check", "codebase health check", "improvement plan", "review my codebase", "what needs fixing", "code quality check", "audit my code", "run an assessment", "arn-assessing", or wants a comprehensive technical assessment of the codebase against stored patterns followed by prioritized improvement execution. Chains to arn-implementing if improvements are identified.
npx claudepluginhub appsvortex/arness --plugin arn-codeThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
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.