Canary Critical Areas — Testing skill for Claude Code
Identify which areas of the codebase carry the most test risk based on churn, dependents, and business-critical signals.
How to install Canary Critical Areas
Installs to ~/.claude/skills/bop-clocktower-canary-canary-critical-areas/SKILL.md
mkdir -p ~/.claude/skills/bop-clocktower-canary-canary-critical-areas && curl -fsSL https://raw.githubusercontent.com/bop-clocktower/canary/HEAD/commands/canary-critical-areas.md -o ~/.claude/skills/bop-clocktower-canary-canary-critical-areas/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Canary Critical Areas does
description: Identify which areas of the codebase carry the most test risk based on churn, dependents, and business-critical signals. argument-hint: "[--diff ] [--save]" allowed-tools: Bash, Read, Glob, Grep
canary-critical-areas
Use the `canary-critical-areas` agent to identify the highest-risk areas.
$ARGUMENTS
Alternatives in Testing
- Gsd To Autoforge Spec — Convert GSD codebase mapping to AutoForge app_spec.txt 1.8k ★
- Workflows — Catalog of multi-agent workflows for development, testing, and business tasks 127 ★
- Aod.Clarify — Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification ques 89 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Canary Test Pipeline
Run the full test intelligence pipeline — assess critical areas, discover edge cases, trace failure impact, ge
Canary CI Ready
Analyse the test suite for CI readiness — coverage depth, flakiness, assertion quality, critical path coverage
Sp.Clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification ques
Skill CI Churn
GitHub Actions cost analyzer & flaky-test detector for pull requests. Measures wasted CI compute, classifies c
Fix Failures
Systematically identify, categorize, and fix test/linter failures using appropriate tools and agents
Validate Hypothesis
Business hypothesis validation skill. Validates ideas through 6 phases (origin check, market confirmation, int
Related Agents
Churn Risk
Identify at-risk customer clusters and the driving signals.
Git Forensics
Analyze git history for code health signals using bbu. Use when the user asks about hotspots, churn, temporal
Swe Bug Assessor
Codebase risk assessor that cross-references complexity, coverage, structural risk factors, and git history to