TuYv/ccpm - Page 57

ln-612-semantic-content-auditor

Checks document semantic content against SCOPE and project goals, coverage gaps, off-topic content, SSOT. Use when auditing documentation relevance.

ln-613-code-comments-auditor

Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.

ln-614-docs-fact-checker

Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.

ln-62-repository-publisher

Validates, commits, pushes, and remotely verifies approved repository changes. Use when publication is requested; not for releases, package publishing, or announcements.

ln-620-codebase-auditor

Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.

ln-621-security-boundary-auditor

Checks application security boundaries: secrets, injection, XSS, input validation, and sensitive env defaults. Use when auditing exploitable code paths.

ln-622-build-delivery-gate-auditor

Checks build, lint, type, test, and CI delivery gate failures. Use when auditing whether the project can reliably ship.

ln-623-duplication-overabstraction-auditor

Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.

ln-624-code-maintainability-hotspot-auditor

Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers. Use when auditing code hotspots.

ln-625-dependency-reuse-auditor

Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.

ln-626-dead-code-pruning-auditor

Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.

ln-627-diagnosability-auditor

Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.

ln-628-concurrency-correctness-auditor

Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.

ln-629-runtime-lifecycle-config-auditor

Checks runtime lifecycle and config validation: bootstrap, shutdown, probes, cleanup, env sync, and fail-fast startup. Use for runtime readiness.

ln-63-release-publisher

Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.

ln-630-test-auditor

Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.

ln-631-test-business-logic-auditor

Detects tests proving platform behavior instead of local product behavior. Use when auditing product-behavior focus.

ln-632-test-e2e-priority-auditor

Audits E2E coverage for critical user-visible journeys and wasteful E2E tests. Use when reviewing E2E journey value.

ln-633-test-value-auditor

Scores each test by portfolio value and returns KEEP/DELETE/MERGE/REWRITE. Use when pruning test-suite cost.

ln-634-test-coverage-auditor

Identifies missing tests for unique critical local logic: money, auth, permissions, data integrity, algorithms, and domain rules. Use when auditing critical logic coverage gaps.

ln-635-test-isolation-auditor

Audits whether test results can be trusted: flakiness, isolation, real external dependencies, time/random/order dependency, and shared state. Use when auditing test trustworthiness.

ln-636-manual-test-auditor

Audits manual test evidence quality: reproducibility, fail-fast behavior, expected evidence/golden files, idempotency, and documentation. Use when auditing manual tests.

ln-637-test-structure-auditor

Audits test maintainability and structure: layout drift, orphan tests, fragmented duplicates, test-to-source mapping, and domain grouping. Use when auditing test suite organization.

ln-638-test-oracle-effectiveness-auditor

Audits assertion strength and test oracles that prove real defects. Use when finding weak tests that execute code but prove little.

ln-64-community-announcer

Drafts and publishes fact-checked GitHub Discussions announcements. Use for releases, updates, or project news; not for release creation or issue responses.

ln-640-pattern-evolution-auditor

Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured summaries.

ln-641-pattern-fitness-auditor

Audits whether one implemented architectural pattern fits project needs and best practices. Use when checking pattern fitness.

ln-642-layer-ownership-boundary-auditor

Checks layer, resource ownership, and orchestration boundaries. Use when auditing architecture boundary enforcement.

ln-71-system-design-baseline-builder

Creates a project baseline of architecture drivers and constraints. Use before design or planning; not for target design, plan review, implementation, or architecture audit.

ln-72-current-architecture-documenter

Documents implemented current-state architecture from repository evidence. Use for onboarding or migration baselines; not for target design, audit verdicts, or code changes.

ln-73-system-design-proposal-builder

Creates a decision-complete target system design from requirements and constraints. Use before implementation planning; not for requirements baselines, reviews, audits, or code changes.

ln-74-architecture-decision-recorder

Records one architecture decision with context, alternatives, tradeoffs, and consequences. Use for a significant choice; not for broad design, audit, or implementation.

ln-75-architecture-diagram-builder

Creates evidence-backed current or target architecture diagrams when the diagram is the primary deliverable. Not for UI design, architecture audit, or invented structure.

ln-76-architecture-migration-planner

Plans a reversible architecture migration with compatibility, data movement, rollout, and rollback. Use for current-to-target transitions; not execution, generic planning, or delivery review.

understand-chat

Use when you need to ask questions about a codebase or understand code using a knowledge graph

understand-dashboard

Launch the interactive web dashboard to visualize a codebase's knowledge graph

understand-diff

Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks

understand-domain

Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing /understand knowledge graph.

understand-explain

Use when you need a deep-dive explanation of a specific file, function, or module in the codebase

understand-figma

Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.