Code health check
This repository demonstrates how to use Claude Code to do real engineering work, not just writing code. 本项目是极客时间专栏 《Claude Code 工程化实战》 的官方配套示例仓库，目标就是： 👉 把 Claude Code 从“对话式编码工具”，变成 可设计、可复用、可治理的工程系统。
npx -y skills add huangjia2019/claude-code-engineering --skill code-health-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Perform a comprehensive code health check on a directory. Use when the user asks to analyze code quality, find issues, or get a health report.
SKILL.md
1.9 KB, as published. Nobody here has run it
Code Health Check
Analyze the codebase at $ARGUMENTS and produce a structured health report.
Checks to Perform
1. File Organization
- Are files reasonably sized? (Flag files > 200 lines)
- Is the directory structure logical?
- Any files that look misplaced?
2. Error Handling
- Are async operations wrapped in try/catch?
- Are errors propagated correctly (not swallowed)?
- Is there a global error handler?
3. Security Basics
- Any hardcoded secrets, API keys, or passwords?
- Any use of
eval()or similar dangerous functions? - Are user inputs validated before use?
4. Code Quality
- Any obvious code duplication (similar blocks in multiple files)?
- Any unused variables or imports?
- Are function signatures reasonable (not too many parameters)?
5. Dependency Hygiene
- Are all imported modules actually used?
- Any circular dependencies?
Severity Levels
Use these to categorize issues:
| Severity | Meaning | Example |
|---|---|---|
| CRITICAL | Must fix immediately | Hardcoded secrets, SQL injection |
| WARNING | Should fix soon | Missing error handling, large files |
| INFO | Nice to improve | Minor duplication, naming conventions |
Output Format
Return a structured report in this exact format:
# Code Health Report: {directory}
## Overall Score: {A/B/C/D/F}
## Summary
- Files analyzed: {count}
- Issues found: {critical} critical, {warning} warnings, {info} info
## Critical Issues
{list each with file:line and description}
## Warnings
{list each with file:line and description}
## Info
{list each with file:line and description}
## Recommendations
{top 3 actionable recommendations}