cc-best

代码库分析，从 Git 历史和代码结构提取编码模式

构建项目并检查错误（修复错误见 /cc-best:fix）

快速恢复上下文，了解项目当前状态

CC-Best Ralph Loop 集成，长时间自主循环

检查点管理，保存和恢复进度

需求澄清智能体，解决 REQ 文档中的待澄清项

死代码清理和代码整理

代码架构文档生成，自动扫描项目结构生成 token 优化的架构图

Git 提交命令，生成规范的 commit message（另见 /cc-best:git-guide 操作指南）

上下文压缩，减少 token 消耗

置信度检查，评估当前阶段的决策质量和完成度

上下文管理，加载项目信息（会话级，另见 /cc-best:memory 管理持久记忆）

UI 设计师智能体，负责界面设计审查和用户体验优化

研发工程师智能体，负责功能编码实现

文档同步，更新项目文档

知识演化，将学习内容聚类生成 Skills/Agents/Commands

GitHub Issue 端到端修复闭环（分析→修复→测试→提交→关闭）

快速修复构建/类型/编译错误，最小化 diff（构建检查见 /cc-best:build）

Git 提交规范和操作指南（参考文档，提交请用 /cc-best:commit）

紧急修复快速通道，跳过 PM/Lead 直接 Dev→Verify→Commit

模型推理和测试

自主迭代循环，自动完成任务序列

研发经理智能体，负责技术方案设计和任务分解

会话学习，从会话中提取可复用模式

项目记忆管理，维护 memory-bank（持久化，另见 /cc-best:context 管理会话上下文）

切换工作模式以适应不同场景（dev/research/review/planning）

切换 Agent 模型策略（质量/均衡/经济）

结对编程模式，与用户协作开发

产品经理智能体，负责需求分析和产品规划

创建 Pull Request

测试工程师智能体，负责质量保证和问题验证

版本发布管理（版本号同步、CHANGELOG 更新、Git Tag）

启动开发服务或应用（快捷启动，完整管理见 /cc-best:service）

配置安全扫描，审计插件自身配置的安全性

自我检查，验证输出质量

开发服务管理（自动检测运行时、启动/停止/重启服务）

配置项目首选包管理器 (npm/pnpm/yarn/bun)

项目初始化，配置 Claude Code 项目和 Hooks

项目状态与诊断信息

组件库审计，评估 skills/rules/commands 的健康度

任务粒度管理，分解和追踪任务

运行项目测试套件

训练机器学习/深度学习模型

综合验证命令，执行构建、类型、Lint、测试、安全检查

System architecture specialist for design decisions, ADR creation, and scalability assessment. Use PROACTIVELY when designing new systems, making architectural decisions, or evaluating technical approaches. <example> user: "我们需要设计一个支持高并发的订单系统" assistant: (invokes architect agent to analyze requirements and design system architecture) </example>

Analyzes build/compile errors and provides minimal targeted fixes. Use PROACTIVELY when build fails, type errors occur, or compilation issues arise. Integrates with /cc-best:verify and /cc-best:fix commands. <example> user: "构建失败了，有 TypeScript 类型错误" assistant: (invokes build-error-resolver agent to diagnose and fix the type errors) </example>

Performs deep code review checking architecture compliance, code quality, and security issues. Use PROACTIVELY after writing or modifying code. MUST BE USED for all significant code changes. <example> user: "审查这次提交的代码变更" assistant: (invokes code-reviewer agent to perform comprehensive code review) </example>

Cleans and simplifies code architecture after feature completion, eliminating redundancy and improving maintainability. Use when code maintenance, refactoring, or dead code cleanup is needed. Invoked after feature completion for code quality improvement. <example> user: "简化用户服务模块的代码，消除重复" assistant: (invokes code-simplifier agent to identify and eliminate redundancy) </example>

Analyzes task complexity, creates implementation plans, and breaks down into minimal executable units. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks. <example> user: "实现用户权限管理模块" assistant: (invokes planner agent to analyze complexity and create implementation plan) </example>

Performs 'unit tests for requirements': validates completeness, clarity, and consistency of requirement documents. Use after /cc-best:pm completes REQ document or when validating requirement quality before design phase. <example> user: "验证需求文档的完整性和一致性" assistant: (invokes requirement-validator agent to check requirement quality) </example>

Checks code for security vulnerabilities including OWASP Top 10, secret leaks, and injection attacks. Use PROACTIVELY before commits when working with authentication, user input, secrets, or API endpoints. Critical for security-sensitive changes. <example> user: "检查登录模块的安全性" assistant: (invokes security-reviewer agent to scan for OWASP vulnerabilities and secret leaks) </example>

Guides test-driven development, helps write test cases, and ensures code quality. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage with write-tests-first methodology. <example> user: "用 TDD 方式实现购物车功能" assistant: (invokes tdd-guide agent to write failing tests first, then implement code) </example>

RESTful API design patterns and best practices. Use when creating endpoints, designing APIs, or implementing routes.

Architecture design skill: ADR records, system design checklists, scalability assessment, architecture patterns. Use for complex system design and architecture decisions.

Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.

Strategic compaction skill: suggests context compression at logical breakpoints. Use to suggest compaction at logical intervals during development sessions.

Database design, query optimization, migrations, and indexing. Use when designing schemas, writing queries, or managing migrations.

Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or troubleshooting incidents.

DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.

Code exploration strategies for understanding unfamiliar codebases. Use when exploring unknown code, debugging, or analyzing architecture.

Frontend patterns: component design, state management, performance, accessibility. Use when building web frontends, components, or client-side apps.

Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.

Extracts reusable patterns from sessions. Use at session end to capture debugging insights and project-specific knowledge.

Model selection strategy and routing. Use when choosing between models for different task types, subagent configurations, or optimizing token cost vs quality tradeoffs.

Native app development strategies including iOS/macOS (Apple platforms), Tauri desktop apps. Use when developing native mobile or desktop applications.

Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).

Research-before-coding workflow: systematically search existing solutions before custom implementation. Use when introducing new libraries, tools, or solving unfamiliar problems.

Cross-validate code, architecture or design decisions using a second model. Use for critical decisions, complex refactoring, security reviews.

Security review skill: comprehensive security checklist and patterns. Use when adding authentication, handling user input, working with secrets, or creating API endpoints.

Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).

Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.

26 hooks across 16 events