diagnose
SolidДиагностика ступени мастерства (Диагност R28, FORM.089 §6.1 v5.0) прямо в VS Code / claude.ai. До 6 вопросов, ~3 мин. Сохраняет cp-профиль в цифровой двойник (browser) или Neon (VS Code). Запускай когда: пилот говорит «пройди диагностику», «какая моя ступень», «/diagnose» — или ПРОАКТИВНО когда видишь пустой cp_profile или нового пользователя без данных.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- TserenTserenov
- Repository
- TserenTserenov/FMT-exocortex-template
- Created
- 5 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
doctor
Audits any project for security, test coverage, and Claude Code automation. 46 checks across 6 layers: secrets, CLAUDE.md, hooks, skills, agents, rules, MCP, CI, memory. Adaptive scoring — auto-detects project maturity (Starter/Growing/Mature/Pro). Diagnoses gaps, prescribes project-specific fixes, applies them. Usage: /doctor — full audit (all 6 layers) /doctor quick — TOP-3 priorities + score (30 seconds) /doctor scan — diagnose only (no changes) /doctor fix — prescribe + apply fixes /doctor layer <N> — audit specific layer (0-5) /doctor verify — health check Triggers: "/doctor", "audit", "setup automation", "configure Claude Code", "project health", "what's missing", "security check", "аудит", "проверь проект"
superdev
涉及本地或远端服务的启动/重启/停止、查看服务日志、排查服务为何没起来或为何报错、诊断故障、管理调试会话、调试本机前端页面(���开浏览器/点击/输入/截图/读 console/network)、对受管语言服务(Go/Node/Python/Java/Kotlin/Rust/C++)做代码断点调试(停在某行看调用栈和变量)、新建受管语言运行时服务(查 provider 与配置 schema)、修改项目/服务配置、或执行 pipeline 部署/回滚时使用——即便用户没说"SuperDev"四个字。只要项目可能已接入 SuperDev,这类请求就应通过 SuperDev 工具完成,而不是用 shell 自己 npm run dev / go run / tail 日志,也不是自己另起浏览器去点页面。涵盖"先确认接管状态再动手"的总纪律、排障主流程、日志工具选型、安全操作纪律(preview->apply、审批门禁)、调试会话生命周期、本机前端浏览器调试、pipeline 部署。
diagnose
When something feels off, type /diagnose and describe the symptom. The skill walks the seven-layer stack (kernel, skills, hooks, daemons, vault, doctrine, principal config) and reports which layer is most likely responsible. Caddy pattern applied to debugging.