Assess Code Quality
Assess existing code for concrete maintainability and correctness risks without changing the implementation.
Use when: Assess existing code for evidence-backed maintainability and correctness risks without changing it. Use for code-quality audits, smell reviews, or prioritizing structural problems; not for implementation.
Install only this skill
Section titled “Install only this skill”arcantry skills link assess-code-quality --scope userThis links only assess-code-quality to the standard user location, ~/.agents/skills. Use --scope repo for one repository, or add --compat claude when that optional alias is needed.
What it helps with
Section titled “What it helps with”- Distinguish material code-quality risks from style preferences and harmless complexity.
- Report each finding with evidence, consequence, confidence, and a proportionate response.
History
Section titled “History”- 2026-09-14 - Add focused code-quality workflows: Arcantry separates evidence-backed code assessment, maintainable structural design and authorized behavior-preserving refactoring into three focused public skills.
Examples
Section titled “Examples”Audit a difficult module
Section titled “Audit a difficult module”Prompt
Use the assess-code-quality skill to review this module for maintainability risks without changing any files.
Expected outcome
The review ranks only evidence-backed findings and preserves the read-only boundary.
Reject a pattern-only complaint
Section titled “Reject a pattern-only complaint”Prompt
Use the assess-code-quality skill to decide whether this procedural implementation is bad because it does not use design patterns.
Expected outcome
The review evaluates concrete consequences and does not treat a missing pattern as a defect.