home / skills / forge-town / skills / check-all-items

check-all-items skill

safe

This skill automatically discovers all best-practice skills and executes their checks, then enforces standardized validation to ensure consistent project

npx playbooks add skill forge-town/skills --skill check-all-items

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

3.3 KB

---
name: check-all-items
description: 自动扫描并执行所有以best-practice结尾的技能，检查项目是否符合最佳实践。通过自动发现机制确保所有相关最佳实践都被检查，并强制执行标准化验证指令提升输出稳定性。
---

# 检查所有项目 (Check All Items)

此技能提供自动化的最佳实践检查流程，通过扫描本地技能库自动发现并执行所有相关的最佳实践检查，确保项目符合所有已定义的标准。

## 核心功能

### 自动发现机制
- 自动扫描本地技能库，查找所有以"best-practice"结尾的技能
- 无需手动维护最佳实践列表，系统自动识别新增技能
- 支持动态扩展，未来新增最佳实践技能会自动被包含

### 逐条执行检查
- 对每个发现的最佳实践技能执行相应的检查
- 按预定义顺序执行，确保依赖关系正确
- 记录每个检查的结果和状态

### 强制验证机制
- 所有检查完成后统一强制执行标准化验证指令
- 确保输出结果经过校验，提升一致性和稳定性
- 提供详细的验证报告和修复建议

## 使用场景

当您需要：
- 全面检查项目是否符合所有最佳实践
- 确保代码质量和架构一致性
- 在开发过程中验证变更是否破坏最佳实践
- 准备代码审查或部署前进行最终检查

## 工作流程

### 1. 自动发现阶段
- 扫描技能库目录
- 识别所有best-practice技能
- 验证技能有效性

*📖 详细机制请参考：[自动发现机制指南](references/auto-discovery-guide.md)*

### 2. 执行检查阶段
- 按优先级顺序执行检查
- 收集每个检查的结果
- 记录发现的问题

*📖 执行流程和错误处理请参考：[执行工作流程](references/execution-workflow.md)*

### 3. 验证阶段
- 执行标准化校验指令
- 生成综合报告
- 提供修复建议

*📖 验证配置和结果处理请参考：[验证机制](references/after-hook-validation.md)*

## 技能依赖

此技能会自动调用以下类型的技能：
- `*-best-practice`：所有最佳实践检查技能
- 验证工具：代码质量检查和测试工具

## 输出格式

### 检查报告
```
📋 项目最佳实践检查报告

✅ 已检查技能：
- dao-best-practice: 通过
- service-best-practice: 通过
- store-best-practice: 通过

⚠️ 发现问题：
- [技能名]: [具体问题描述]

🔧 修复建议：
- [具体可操作的修复步骤]

📊 验证结果：
- [标准化验证指令的执行结果]
```

## 配置选项

### 验证指令
- 默认执行：`npm run quality`
- 可自定义：通过技能配置指定其他验证命令

### 检查范围
- 默认：检查所有活跃的best-practice技能
- 可过滤：指定要包含或排除的技能

## 故障排除

### 常见问题
- **技能未被发现**：检查技能名称是否以"best-practice"结尾
- **验证失败**：确认项目中存在指定的验证脚本
- **执行超时**：检查网络连接或外部服务依赖

### 调试模式
启用详细日志查看每个检查步骤的执行情况。

## 扩展性

### 添加新最佳实践
1. 创建新的`*-best-practice`技能
2. 确保技能符合标准接口
3. 系统会自动在下次检查时包含新技能

### 自定义验证
修改技能配置中的验证指令以适应项目需求。

Overview

This skill automates discovery and execution of all skills whose names end with "best-practice" to verify a project meets defined standards. It runs each detected best-practice check in order, enforces a standardized validation step, and produces a consolidated report with findings and remediation suggestions. The goal is consistent, repeatable verification of code quality and architecture before review or deployment.

How this skill works

The skill scans a local skills directory to auto-discover any skill whose name ends with "best-practice." It executes each discovered check in a predefined order, records results and statuses, then runs a uniform validation command (default: npm run quality) to standardize output verification. Finally, it aggregates results into a single report that lists passed checks, issues found, and actionable fix recommendations.

When to use it

Run a full project validation before code review or deployment.
Verify recent changes did not break established best practices.
Continuously enforce quality gates in CI or pre-merge checks.
Ensure new best-practice checks are automatically included without manual updates.
Generate a unified compliance and remediation report for stakeholders.

Best practices

Keep best-practice skill names suffixed with "-best-practice" so they are discoverable.
Define an execution priority when checks have dependencies to ensure correct ordering.
Provide a reliable validation command (default npm run quality) and make it configurable.
Enable detailed logging or debug mode when troubleshooting discovery or execution failures.
Add clear, actionable remediation steps in each best-practice skill to speed fixes.

Example use cases

Pre-deployment sweep that runs all best-practice checks and a standardized validation to produce a compliance report.
CI pipeline stage that auto-discovers and executes best-practice skills to gate merges.
Developer local command to validate that a branch adheres to all active best practices before opening a PR.
Periodic repository audit to detect regressions or newly introduced best-practice violations.

FAQ

What if a best-practice skill is not discovered?

Ensure the skill file or package name ends with "best-practice" and that the skills directory path is correct. Enable debug logs for discovery details.

Can I change the validation command?

Yes. The validation command defaults to npm run quality but is configurable in the skill settings to match your project tooling.