charm-review

Review Charm code for Cantrip conventions and UK English standards.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/tonyandrewmeyer/cantrip --skill charm-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: charm-review
Source: https://github.com/tonyandrewmeyer/cantrip/tree/main/.agents/skills/charm-review
Command: npx skills add https://github.com/tonyandrewmeyer/cantrip --skill charm-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews Cantrip charm code for correctness and project conventions to prevent defects and maintain consistency across the codebase.

Core Features & Use Cases

  • Enforces UK English spelling, documentation standards, and explanatory comments that justify design choices.
  • Detects architectural pattern deviations, ensures proper module layout, and highlights code smells with concrete fixes.
  • Use Case: when a Charm is updated or a subagent changes, run the review to surface issues before merge and keep the project aligned with COS and tracing requirements.

Quick Start

Review the latest charm code changes and output actionable issues and fixes.

Frequently Asked Questions about charm-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce coding standards and architecture rules in charm code?

To enforce coding standards in charm code, run a static analysis review that detects architectural deviations and highlights code smells. This process identifies pattern violations and provides concrete, actionable fixes to maintain project consistency before merging changes.

How does static analysis detect code smells and provide actionable fixes?

Static analysis detects code smells by evaluating the codebase against defined architectural patterns and quality conventions. It highlights deviations and outputs concrete, actionable fixes that align module layout and design choices with project standards.

Can I check Cantrip charm code for UK English spelling and documentation standards?

Yes, you can check Cantrip charm code for UK English spelling and documentation standards. The review process applies these conventions across the codebase to ensure explanatory comments justify design choices and maintain consistency.

What is the best way to review charm code changes before merging subagent updates?

The best way to review charm code changes before merging subagent updates is to run an automated audit. This surfaces issues related to COS integration and tracing requirements, ensuring changes align with project conventions before merge.

Does the code review process ensure changes align with COS integration and observability goals?

Yes, the code review process ensures changes align with COS integration and observability goals. It evaluates the charm codebase against these specific requirements, surfacing deviations and providing fixes to maintain tracing and integration standards.