メニュー
Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ludo-technologies/pyscn --skill health-checkコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Analyze Python module architecture using pyscn - class coupling (CBO), cohesion (LCOM), dependency cycles, and module communities. Use when user asks about architecture, module structure, coupling, circular dependencies, or which files to review or change together.
Run the pyscn command-line tool for Python code quality analysis - CI/CD quality gates, HTML/JSON/CSV reports, full analysis runs, and project configuration. Use when user wants a CI check, a shareable report file, or to configure pyscn for a project.
Find refactoring targets in Python code using pyscn - duplicate code (clones), overly complex functions, and dead code. Use when user asks about refactoring, code duplication, complexity hotspots, unreachable code, or cleaning up a codebase.
| name | health-check |
| description | Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison. |
Run the pyscn CLI to give a quick, quantified picture of code quality. No install needed:
uvx pyscn@latest analyze <path>
The summary output includes a health score (0-100), a letter grade (A-F), and per-category metrics.
| User Request | Command |
|---|---|
| "How healthy is this code?" | uvx pyscn@latest analyze <path> |
| "Give me a quality overview" | Same command; walk through the category breakdown |
| "Did my refactoring improve quality?" | Run before and after, compare scores |
For machine-readable detail add --json. Report files are NOT written to stdout. They go to .pyscn/reports/ under the current working directory and the path is printed on completion; read that file.
refactoring, module structure → architecture-review.Always explain the score in plain terms and suggest the highest-impact next step.
If the pyscn-mcp MCP server is connected, you can use its tools instead of the CLI: get_health_score (score + grade) or analyze_code (output_mode: "summary" gives the health score plus high-level metrics per category). Results are returned inline with no report files.