[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS1QAM16KYANXE9CMHKA3M":3,"skill-same:01M7CS1QAM16KYANXE9CMHKA3M":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CS1QAM16KYANXE9CMHKA3M","codehealth-mcp",null,"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\u002FPR.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fcodehealth-mcp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: codehealth-mcp\ndescription: 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\u002FPR.\nmetadata:\n  origin: community\n---\n\n# Code Health MCP (CodeScene)\n\nStructural maintainability feedback for AI-assisted coding. Complements style\u002Flint skills (`coding-standards`, `plankton-code-quality`) with **design-level** health scores and regression gates.\n\n**Upstream:** [codescene-oss\u002Fcodescene-mcp-server](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server)\n**Package:** `@codescene\u002Fcodehealth-mcp` (stdio via npx)\n\n## Security and boundaries\n\n**Opt-in (ECC):** The `codescene` block in `mcp-configs\u002Fmcp-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\u002Fsync with `ECC_DISABLED_MCPS=codescene,...`.\n\n**Credentials:** No bundled token. Set `CS_ACCESS_TOKEN` yourself (see [getting-a-personal-access-token.md](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server\u002Fblob\u002Fmain\u002Fdocs\u002Fgetting-a-personal-access-token.md) in the upstream repo). Never commit tokens to the repo.\n\n**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 `analyze_change_set`). They do not run by themselves. For standalone mode, follow upstream privacy docs: [codescene-mcp-server README](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server#frequently-asked-questions) and [CodeScene policies](https:\u002F\u002Fcodescene.com\u002Fpolicies). Do not use this skill for secrets, credentials, or paths you do not want analyzed.\n\n**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\u002Ftests\u002Fverification-loop for gating when MCP is down. Re-enable checks once the server connects.\n\n## When to Use\n\n- User asks to **review code quality**, **refactor** a file, or check if **AI changes degraded** maintainability\n- Before editing a **hotspot**, legacy module, or unfamiliar file\n- Before **commit** or **pull request** when you need a maintainability safeguard\n- After a large agent-written diff — verify Code Health did not regress\n- Pair with `verification-loop`, `tdd-workflow`, or `\u002Fquality-gate` as a structural check (not a replacement for tests\u002Flint)\n\n## When to Activate\n\nSame triggers as **When to Use** above — this heading is what ECC uses for skill auto-activation.\n\n## How It Works\n\n### 1. Connect the MCP server\n\nCopy the `codescene` entry from `mcp-configs\u002Fmcp-servers.json` into your harness MCP config.\n\n**Claude Code** (`~\u002F.claude.json` → `mcpServers`):\n\n```json\n\"codescene\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"@codescene\u002Fcodehealth-mcp\"],\n  \"env\": {\n    \"CS_ACCESS_TOKEN\": \"YOUR_CS_ACCESS_TOKEN_HERE\"\n  }\n}\n```\n\n**Project-scoped:** merge the same block into `.mcp.json` at the repo root.\n\nToken setup is documented in the upstream repo (link above). Standalone mode does not require a paid CodeScene platform account for the four tools listed below. Restart the session and confirm the `codescene` server is connected before relying on scores.\n\n### 2. Call standalone tools only\n\n| Tool | When to use |\n|------|-------------|\n| `code_health_review` | Full structural analysis **before** modifying a file |\n| `code_health_score` | Quick numeric score after each change (delta check) |\n| `pre_commit_code_health_safeguard` | Block commits that introduce Code Health regressions |\n| `analyze_change_set` | Branch-level check **before** opening a PR |\n\nDo **not** call platform-only tools (e.g. repository-wide technical debt hotspot lists). Do **not** reference `delta_analysis` — not available on standalone.\n\n### 3. Interpret scores (1–10)\n\n| Range | Meaning | Agent behavior |\n|-------|---------|----------------|\n| **9.0–10.0** | Green — healthy | Safer to extend; still prefer vertical slices |\n| **4.0–8.9** | Yellow — debt | Tread carefully; no drive-by refactors |\n| **1.0–3.9** | Red — severe debt | Narrow scope only |\n\n### 4. Run the feedback loop\n\n**Before touching a file**\n\n1. Run `code_health_review` on the target path.\n2. Record baseline score and listed code smells.\n3. Plan the smallest change that addresses the task.\n\nScope by score: **below 5** — minimal diff only; **5–7** — no broad refactors; **above 7** — safer to refactor, still verify after each edit.\n\n**After each change**\n\n1. Run `code_health_score` on the same file.\n2. Compare to the baseline from `code_health_review`.\n3. If the score **regressed**, fix before continuing. Never mark the task done while the score is lower than when you started.\n\n**Before every commit** — run `pre_commit_code_health_safeguard` on the repository path.\n\n**Before a PR** — run `analyze_change_set` against the base branch (e.g. `main`).\n\n## Examples\n\n### Example: Flask maintainability improvement\n\nOn `pallets\u002Fflask`, an agent loop using only standalone tools:\n\n1. `code_health_review` on a target module (baseline **4.82**)\n2. Targeted refactor addressing listed smells\n3. `code_health_score` after each edit\n4. `pre_commit_code_health_safeguard` before commit\n5. `analyze_change_set` before PR\n\nResult: Code Health **4.82 → 9.1** (free standalone token only).\n\n### Example: AGENTS.md enforcement block\n\nPaste into the project `AGENTS.md` or `CLAUDE.md`:\n\n```md\n## Code Health (CodeScene MCP)\n\nBefore modifying any file: run `code_health_review`, note score and issues.\n\n- Score below 5: problematic range — scope changes narrowly.\n- Score 5–7: warning range — no broad refactors.\n\nAfter each change: run `code_health_score` to verify delta.\n\n- If score regressed: fix before continuing; never declare done if score dropped.\n\nBefore every commit: run `pre_commit_code_health_safeguard`.\n\nBefore PR: run `analyze_change_set`.\n```\n\n### Example: anti-patterns vs correct loop\n\n```markdown\n# BAD: Edit first, check later\n[large refactor without code_health_review]\n\n# BAD: Ignore score drop\n\"Tests pass\" → mark task done while Code Health decreased\n\n# BAD: Broad refactor on red-score file (below 5)\nDrive-by cleanup across the module\n\n# GOOD: review → small change → score → commit safeguard → analyze_change_set\n```\n\n## Pairing with ECC\n\n| ECC skill \u002F flow | Code Health MCP role |\n|------------------|----------------------|\n| `coding-standards` | Style\u002Fnaming; Code Health = structure\u002Fcomplexity |\n| `plankton-code-quality` | Write-time lint\u002Fformat; Code Health = pre\u002Fpost edit structural gate |\n| `verification-loop` \u002F `\u002Fquality-gate` | Add structural regression check before \"done\" |\n| `security-review` | Security vs maintainability — use both when relevant |\n| `tdd-workflow` | Tests pass ≠ healthy design — check score after refactors |\n\n**Context tip:** ECC recommends keeping MCP count low. Enable `codescene` when doing substantive edits; disable when not needed.\n\n## Related Skills\n\n- `coding-standards` — baseline conventions\n- `plankton-code-quality` — write-time lint\u002Fformat hooks\n- `verification-loop` — build\u002Ftest\u002Flint gate\n- `tdd-workflow` — test-first development\n- `security-review` — security checklist\n- `documentation-lookup` — library docs via Context7 (orthogonal)\n","# Code Health MCP (CodeScene)\n\nStructural maintainability feedback for AI-assisted coding. Complements style\u002Flint skills (`coding-standards`, `plankton-code-quality`) with **design-level** health scores and regression gates.\n\n**Upstream:** [codescene-oss\u002Fcodescene-mcp-server](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server)\n**Package:** `@codescene\u002Fcodehealth-mcp` (stdio via npx)\n\n## Security and boundaries\n\n**Opt-in (ECC):** The `codescene` block in `mcp-configs\u002Fmcp-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\u002Fsync with `ECC_DISABLED_MCPS=codescene,...`.\n\n**Credentials:** No bundled token. Set `CS_ACCESS_TOKEN` yourself (see [getting-a-personal-access-token.md](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server\u002Fblob\u002Fmain\u002Fdocs\u002Fgetting-a-personal-access-token.md) in the upstream repo). Never commit tokens to the repo.\n\n**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 `analyze_change_set`). They do not run by themselves. For standalone mode, follow upstream privacy docs: [codescene-mcp-server README](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server#frequently-asked-questions) and [CodeScene policies](https:\u002F\u002Fcodescene.com\u002Fpolicies). Do not use this skill for secrets, credentials, or paths you do not want analyzed.\n\n**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\u002Ftests\u002Fverification-loop for gating when MCP is down. Re-enable checks once the server connects.\n\n## When to Use\n\n- User asks to **review code quality**, **refactor** a file, or check if **AI changes degraded** maintainability\n- Before editing a **hotspot**, legacy module, or unfamiliar file\n- Before **commit** or **pull request** when you need a maintainability safeguard\n- After a large agent-written diff — verify Code Health did not regress\n- Pair with `verification-loop`, `tdd-workflow`, or `\u002Fquality-gate` as a structural check (not a replacement for tests\u002Flint)\n\n## When to Activate\n\nSame triggers as **When to Use** above — this heading is what ECC uses for skill auto-activation.\n\n## How It Works\n\n### 1. Connect the MCP server\n\nCopy the `codescene` entry from `mcp-configs\u002Fmcp-servers.json` into your harness MCP config.\n\n**Claude Code** (`~\u002F.claude.json` → `mcpServers`):\n\n```json\n\"codescene\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"@codescene\u002Fcodehealth-mcp\"],\n  \"env\": {\n    \"CS_ACCESS_TOKEN\": \"YOUR_CS_ACCESS_TOKEN_HERE\"\n  }\n}\n```\n\n**Project-scoped:** merge the same block into `.mcp.json` at the repo root.\n\nToken setup is documented in the upstream repo (link above). Standalone mode does not require a paid CodeScene platform account for the four tools listed below. Restart the session and confirm the `codescene` server is connected before relying on scores.\n\n### 2. Call standalone tools only\n\n| Tool | When to use |\n|------|-------------|\n| `code_health_review` | Full structural analysis **before** modifying a file |\n| `code_health_score` | Quick numeric score after each change (delta check) |\n| `pre_commit_code_health_safeguard` | Block commits that introduce Code Health regressions |\n| `analyze_change_set` | Branch-level check **before** opening a PR |\n\nDo **not** call platform-only tools (e.g. repository-wide technical debt hotspot lists). Do **not** reference `delta_analysis` — not available on standalone.\n\n### 3. Interpret scores (1–10)\n\n| Range | Meaning | Agent behavior |\n|-------|---------|----------------|\n| **9.0–10.0** | Green — healthy | Safer to extend; still prefer vertical slices |\n| **4.0–8.9** | Yellow — debt | Tread carefully; no drive-by refactors |\n| **1.0–3.9** | Red — severe debt | Narrow scope only |\n\n### 4. Run the feedback loop\n\n**Before touching a file**\n\n1. Run `code_health_review` on the target path.\n2. Record baseline score and listed code smells.\n3. Plan the smallest change that addresses the task.\n\nScope by score: **below 5** — minimal diff only; **5–7** — no broad refactors; **above 7** — safer to refactor, still verify after each edit.\n\n**After each change**\n\n1. Run `code_health_score` on the same file.\n2. Compare to the baseline from `code_health_review`.\n3. If the score **regressed**, fix before continuing. Never mark the task done while the score is lower than when you started.\n\n**Before every commit** — run `pre_commit_code_health_safeguard` on the repository path.\n\n**Before a PR** — run `analyze_change_set` against the base branch (e.g. `main`).\n\n## Examples\n\n### Example: Flask maintainability improvement\n\nOn `pallets\u002Fflask`, an agent loop using only standalone tools:\n\n1. `code_health_review` on a target module (baseline **4.82**)\n2. Targeted refactor addressing listed smells\n3. `code_health_score` after each edit\n4. `pre_commit_code_health_safeguard` before commit\n5. `analyze_change_set` before PR\n\nResult: Code Health **4.82 → 9.1** (free standalone token only).\n\n### Example: AGENTS.md enforcement block\n\nPaste into the project `AGENTS.md` or `CLAUDE.md`:\n\n```md\n## Code Health (CodeScene MCP)\n\nBefore modifying any file: run `code_health_review`, note score and issues.\n\n- Score below 5: problematic range — scope changes narrowly.\n- Score 5–7: warning range — no broad refactors.\n\nAfter each change: run `code_health_score` to verify delta.\n\n- If score regressed: fix before continuing; never declare done if score dropped.\n\nBefore every commit: run `pre_commit_code_health_safeguard`.\n\nBefore PR: run `analyze_change_set`.\n```\n\n### Example: anti-patterns vs correct loop\n\n```markdown\n# BAD: Edit first, check later\n[large refactor without code_health_review]\n\n# BAD: Ignore score drop\n\"Tests pass\" → mark task done while Code Health decreased\n\n# BAD: Broad refactor on red-score file (below 5)\nDrive-by cleanup across the module\n\n# GOOD: review → small change → score → commit safeguard → analyze_change_set\n```\n\n## Pairing with ECC\n\n| ECC skill \u002F flow | Code Health MCP role |\n|------------------|----------------------|\n| `coding-standards` | Style\u002Fnaming; Code Health = structure\u002Fcomplexity |\n| `plankton-code-quality` | Write-time lint\u002Fformat; Code Health = pre\u002Fpost edit structural gate |\n| `verification-loop` \u002F `\u002Fquality-gate` | Add structural regression check before \"done\" |\n| `security-review` | Security vs maintainability — use both when relevant |\n| `tdd-workflow` | Tests pass ≠ healthy design — check score after refactors |\n\n**Context tip:** ECC recommends keeping MCP count low. Enable `codescene` when doing substantive edits; disable when not needed.\n\n## Related Skills\n\n- `coding-standards` — baseline conventions\n- `plankton-code-quality` — write-time lint\u002Fformat hooks\n- `verification-loop` — build\u002Ftest\u002Flint gate\n- `tdd-workflow` — test-first development\n- `security-review` — security checklist\n- `documentation-lookup` — library docs via Context7 (orthogonal)\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fcodehealth-mcp","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill codehealth-mcp",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill codehealth-mcp",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill codehealth-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fcodehealth-mcp\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]