Menu
Use BEFORE reading multiple files to understand code. Reminds you to use codebase-analyzer agent instead of manual file reading.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Determine feature slug interactively by auto-detecting next number and prompting user for description
Share personal documents to the shared namespace with atomic git commit and push
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
| name | before-code-analysis |
| description | Use BEFORE reading multiple files to understand code. Reminds you to use codebase-analyzer agent instead of manual file reading. |
STOP: You're about to read multiple files to understand how something works.
The codebase-analyzer agent is specifically designed for understanding code implementation. It will read files in context and explain how systems work.
Read(file_path="src/auth/handler.js")
Read(file_path="src/auth/service.js")
Read(file_path="src/auth/middleware.js")
[manually piecing together how auth works]
Task(
subagent_type="codebase-analyzer",
prompt="Analyze how the authentication system works, including handlers, services, and middleware",
description="Analyze auth system"
)
Only read files manually when:
For understanding systems or flows, use codebase-analyzer.