Agent skill · software engineering · affaan-m
codehealth-mcp
Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.
Why this skill is useful
Adds specific commands for analyzing code health and maintaining structural quality that the AI wouldn't reliably generate on its own.
What it needs
Requires @codescene/codehealth-mcp installed locally. Requires codescene account access. About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Code Health MCP (CodeScene) Structural maintainability feedback for AI-assisted coding. Complements style/lint skills (coding-standards, plankton-code-quality) with design-level health scores and regression gates. Upstream: codescene-oss/codescene-mcp-server Package: @codescene/codehealth-mcp (stdio via npx) Security and boundaries Opt-in (ECC): The codescene block in mcp-configs/mcp-servers.json is a template only. ECC plugin installs do not auto-enable bundled MCP servers. Copy the entry into your config only if you want it. You can exclude it during ECC install/sync with ECCDISABLEDMCPS=codescene,.... Credentials: No bundled token. Set CSACCESSTOKEN yourself (see getting-a-personal-access-token.md in the upstream repo). Never commit tokens to the repo. What the tools read: When invoked, tools analyze files and git state in the local repository you point them at (paths you pass, plus branch context for analyzechangeset). They do not run by themselves. For standalone mode, follow upstream privacy docs: codescene-mcp-server README and CodeScene policies. Do not use this skill for secrets, credentials, or paths you do not want analyzed. If the MCP is unavailable (offline, bad token, server crash): Do not invent Code Health scores. Tell the user the check was skipped. Continue only with explicit user approval. Prefer lint/tests/verification-loop for gating when MCP is down. Re-enable checks once the server connects. When to Use User asks to review code quality, refactor a file, or check if AI changes degraded maintainability Before editing a hotspot, legacy module, or unfamiliar file Before commit or pull request when you need a maintainability safeguard After a large agent-written diff — verify Code Health did not regress Pair with verification-loop, tdd-workflow, or /quality-gate as a structural check (not a replacement for tests/lint) When to Activate Same triggers as When to Use above — this heading is what ECC uses for skill auto-activation. How It Works 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/codehealth-mcp