# Project Health Check

> Explicit-invocation broad repository diagnosis across architecture, correctness, security, performance, dependencies, tests, and general release risk. Do not trigger for a bounded file, error, diff, or simple request. Use a specialized review for one dependency upgrade, API contract, migration, dead-code candidate, security surface, performance regression, configuration scope, or release candidate. 仅显式调用的全仓库诊断，覆盖架构、正确性、安全、性能、依赖、测试和一般发布风险。不得因单个文件、明确报错、Diff 或简单请求而触发。单一依赖升级、API 契约、迁移、死代码候选、安全边界、性能回归、配置范围或候选版本应使用对应专项 Skill。

- Skill: `dss-time/project-health-check` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add dss-time/project-health-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dss-time/project-health-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: dss-time (https://skillmd.com/u/dss-time)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dss-time/project-health-check

---


# English

## Execution Contract

Default to `standard`; explicit invocation is required.
Complete one primary task by default. Continue an authorized end-to-end workflow within each Skill's permissions; Router remains recommendation-only. Pause for new material decisions or scope, not authorization already given.
Validate according to actual risk; security, production, migrations, releases and other high-risk work use `audit`. Read `references/execution-modes.en.md` only when mode selection is unclear.

# Project Health Check

Use this skill for a broad repository diagnosis. Do not start by rewriting code.

## Review Dimensions

- Architecture risk
- Type risk
- Test gaps
- Security risk
- Performance risk
- Dependency risk
- Maintainability issues
- Dead or redundant code
- Release risk

## Workflow

1. Inspect metadata, scripts, test config, CI, and source layout.
2. Identify core modules and shared utilities.
3. Search references before calling code unused.
4. Check test coverage signals and release commands when available.
5. Prioritize by real user or release risk.
6. Report P0/P1/P2/P3 issues with evidence.

# Output Format

1. Overall health conclusion
2. Health score table
3. P0/P1/P2/P3 issues with evidence
4. Architecture and module boundary risks
5. Redundant or possible dead code
6. Security and stability risks
7. Performance issues
8. Test gaps
9. Release readiness checks
10. Recommended roadmap
11. Final recommendation

# 简体中文

## 执行契约

默认使用 `standard`；仅允许用户显式调用。
默认完成一个主任务。用户已授权完整流程时，在各 Skill 权限内连续完成；Router 仍只推荐。新重大决策或超出授权时暂停，不重复索取已有授权。
按实际风险选择验证；安全、生产、迁移、发布等高风险工作使用 `audit`。模式不明确时才读取 `references/execution-modes.zh-CN.md`。

# 项目体检

用于对仓库做整体诊断。不要一开始就重写代码。

## 检查维度

- 架构风险
- 类型风险
- 测试缺口
- 安全风险
- 性能风险
- 依赖风险
- 可维护性问题
- 死代码或冗余代码
- 发布风险

## 工作流程

1. 检查元数据、脚本、测试配置、CI 和源码结构。
2. 识别核心模块和共享工具。
3. 在判断代码未使用前先搜索引用。
4. 检查测试覆盖信号和发布命令。
5. 按真实用户风险或发布风险排序。
6. 按 P0/P1/P2/P3 输出问题和证据。

# 输出格式

1. 整体健康结论
2. 健康评分表
3. 带证据的 P0/P1/P2/P3 问题
4. 架构和模块边界风险
5. 冗余代码或疑似死代码
6. 安全和稳定性风险
7. 性能问题
8. 测试缺口
9. 发布准备度检查
10. 推荐路线图
11. 最终建议