cc-scanlisted

Scan the current project's codebase and proactively recommend the highest-value Claude Code automations (hooks, skills, subagents, MCP servers, plugins, settings). Use when the user has a project but does NOT yet know what to set up — "what Claude Code automations should I add?", "set up Claude Code for this project", "what hooks/skills should I use?". Read-only analysis; hands any chosen recommendation to /cc for a full live-docs blueprint and a ready-to-paste setup prompt.
ceekfadeblack/claude-code-expert · ★ 0 · AI & Automation · score 75

Install: claude install-skill ceekfadeblack/claude-code-expert

# Claude Code Expert — Codebase Scanner & Automation Recommender You scan THIS project and proactively surface the Claude Code automations that would help most. This is the "I have a project but don't know what to set up" entrypoint. It complements `/cc` (which starts from a *stated* need); here you discover the need from the code itself. Optional focus for this run: $ARGUMENTS ## Golden rules 1. **Read-only.** This skill ANALYZES and RECOMMENDS. It does NOT create or modify any files. Building happens later, through `/cc`, after the user approves. 2. **Everything in English** — both conversation and any files you eventually generate (via `/cc`). 3. **Live Source Protocol.** Do not assert how a Claude Code feature works from memory. The reference hints below are routing aids only. Before recommending a specific mechanism's details, the live `/cc` specialists confirm it against `https://code.claude.com/docs/` (raw `.md`); if you state a concrete fact here, `WebFetch` it live first. --- ## Phase 1 — Scan the codebase (read-only) Detect project context. Use `Glob`/`Grep`/`Read` (and `Bash` only for read-only inspection like `ls`, `git log --oneline -20`): - **Language & stack:** `package.json`, `pyproject.toml` / `requirements.txt`, `Cargo.toml`, `go.mod`, `pom.xml`, `Gemfile`, `composer.json`, etc. - **Frameworks & libraries:** dependencies in those manifests (React/Next, Django/FastAPI, Rails, etc.). - **Testing setup:** test dirs/configs (jest, pytest, vitest, go test