Results for “code-health”

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Skill for the Health area of paddock. 28 symbols across 6 files.

Create medical coding guides for billing accuracy. TRIGGERS - Use when user needs help with coding-guide related tasks.

Code Cleanup

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Proactive self-monitoring of infrastructure, services, and health. Tracks disk/memory/load, service health, cron job status, recent errors. Auto-fixes safe issues. Triggers on: health check, heartbeat, monitor status, service status, infrastructure check.

Create medical coding guides for billing accuracy. TRIGGERS - Use when user needs help with coding-guide related tasks.

This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

Improves code readability and maintainability by applying SOLID principles, meaningful naming, small functions, proper error handling, and DRY practices.

扫描全 wiki 发现健康问题，生成修复建议报告（覆盖全 9 种 entity + graph 一致性）

Transforms working code into clean, readable, and maintainable code following Robert C. Martin's principles.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Provides code review best practices, checklists, and example feedback for quality, security, performance, and maintainability.

Conducts multi-axis code review across correctness, readability, architecture, security, and performance before merging any change.

Simplify code by reducing complexity while preserving exact behavior, making it easier to read, understand, modify, and debug.

Run a comprehensive code review

Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

Skill for the Governance area of paddock. 28 symbols across 23 files.

Code Craft

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

Review technical and strategy documents for codebase drift, strategic alignment, cross-document conflicts, simplification opportunities, engineering quality, and document organization. Use when auditing whether docs should be kept, updated, merged, split, moved, archived, or deleted.

Run mutation testing against a project's test suite to verify the tests actually catch failures when source code is broken. Use after major test changes, before declaring a suite "good", or when coverage % looks healthy but you suspect tests aren't catching real bugs.

Manage MarketingClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push debounce, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning `.github/workflows/*`, `docs/ci.md`, CI runner labels, matrix `max-parallel`, ClawSweeper/Blacksmith burst protection, CodeQL runner placement, or investigating slow/queued MarketingClaw CI.

Use this skill when the user asks about US-Canada cross-border CMV operations — CVOR (Commercial Vehicle Operator's Registration), NSC (National Safety Code), Ontario / Quebec / BC specific rules, US carrier obtaining Canadian operating authority, FAST card for drivers, customs (CBSA), Health Canada hazmat, and how Transport Canada equivalents differ from US FMCSA. Reference USMCA + Transport Canada NSC 14.

Full project analysis for an unfamiliar Sage/Acorn/Lando project — discovers CPTs, routes, ACF field groups, Livewire components, Service Providers, active plans, installed packages; produces a structured project overview with health status and recommended next steps. Invoke for: "/onboarding", "I'm new to this project", "what does this project do", "show me what exists", "project overview", "orient me to this codebase", "what exists in this project". Skip when: you already know the project — the session-start hook already provided basic stack info; invoke the target skill directly instead.