analyze
Systematic multi-step codebase analysis producing prioritized findings with file-line evidence. Covers architecture reviews, security assessments, and code quality evaluations through guided exploration, investigation planning, and synthesis.
- License 许可
- MIT
- 最近更新
- 2026-03-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- analyze
- model
- claude-opus-4-6[1m]
- agents
- [ "analyst", "orchestrator" ]
- license
- MIT
- metadata
- { "version": "1.1.0", "timelessness": "8/10" }
- description
- Systematic multi-step codebase analysis producing prioritized findings with file-line evidence. Covers architecture reviews, security assessments, and code quality evaluations through guided exploration, investigation planning, and synthesis.
- allowed-tools
- [ "Read", "Grep", "Glob", "Bash", "Agent" ]
- user-invocable
- true
02 资源文件 2
- 参考文档references/DEVELOPMENT.md2.4 KB
- 脚本scripts/analyze.ts21.0 KB
03 SKILL.md 正文
Analyze Skill
When this skill activates, IMMEDIATELY invoke the script. The script IS the workflow. Do NOT explore the codebase first.
Triggers
analyze this codebase- architecture and quality focusreview code quality- quality focusrun security assessment- security focusarchitecture review of this system- architecture focusfind code smells- quality focus
Quick Reference
| Input | Focus | Minimum Steps |
|---|---|---|
| Architecture review | Structure, dependencies, layering | 6 |
| Security assessment | Input validation, auth, data handling | 7-9 |
| Code quality | Duplication, complexity, test gaps | 6-7 |
| Broad investigation | All dimensions | 9-12 |
Security
When using the Bash tool, all arguments containing variable or user-provided input MUST be quoted to prevent command injection vulnerabilities. Refer to the repository style guide on Command Injection Prevention (CWE-78).
WRONG: grep $PATTERN /some/path
CORRECT: grep -- "$PATTERN" /some/path
When to Use
Use this skill when:
- Investigation spans multiple files or components
- Analysis requires structured multi-step exploration
- Findings need prioritization by severity with file:line evidence
Use direct code reading instead when:
- Checking a single file or function
- The question has a known, specific location
- A quick grep or symbol search answers the question
Scripts
| Script | Purpose | Exit Codes |
|---|---|---|
scripts/analyze.ts |
Multi-step guided analysis with exploration, investigation, and synthesis | 0=success, 1=invalid input |
Invocation
bun run ${CLAUDE_SKILL_DIR}/scripts/analyze.ts \
--step-number 1 \
--total-steps 6 \
--thoughts "Starting analysis. User request: <describe what user asked to analyze>"
| Argument | Required | Description |
|---|---|---|
--step-number |
Yes | Current step (starts at 1) |
--total-steps |
Yes | Minimum 6; adjust as script instructs |
--thoughts |
Yes | Accumulated state from all previous steps |
Process
The script outputs REQUIRED ACTIONS at each step. Follow them exactly.
Phase 1: Exploration (Step 1)
Delegate to Explore agent(s). The script determines scope and parallelism. Wait for all agents, then re-invoke ${CLAUDE_SKILL_DIR}/scripts/analyze.ts with --step-number 1, including the Explore results in --thoughts.
Phase 2: Focus Selection (Step 2)
Classify investigation areas by dimension (architecture, performance, security, quality). Assign priorities P1-P3. Estimate total steps.
Phase 3: Investigation Planning (Step 3)
Commit to specific files, questions, and hypotheses per focus area. This creates a contract verified in the verification phase.
Phase 4: Deep Analysis (Steps 4 to N-2)
Execute the investigation plan. Read files, collect evidence with file:line references and quoted code. Trace root causes across files.
Phase 5: Verification (Step N-1)
Audit completeness against step 3 commitments. Identify gaps. If gaps exist, increase total-steps and return to deep analysis.
Phase 6: Synthesis (Step N)
Consolidate verified findings by severity (critical, high, medium, low). Identify systemic patterns. Produce prioritized action plan.
Example Sequence
# Step 1: Start, script instructs you to explore first
bun run ${CLAUDE_SKILL_DIR}/scripts/analyze.ts --step-number 1 --total-steps 6 \
--thoughts "Starting analysis of auth system"
# [Follow REQUIRED ACTIONS: delegate to Explore agent, wait for results]
# Step 1 again with explore results
bun run ${CLAUDE_SKILL_DIR}/scripts/analyze.ts --step-number 1 --total-steps 6 \
--thoughts "Explore found: Flask app, SQLAlchemy, auth/ dir..."
# Step 2+: Continue following script output
bun run ${CLAUDE_SKILL_DIR}/scripts/analyze.ts --step-number 2 --total-steps 7 \
--thoughts "[accumulated state from step 1] Focus: security P1, quality P2"
Anti-Patterns
| Avoid | Why | Instead |
|---|---|---|
| Exploring the codebase before invoking the script | Script orchestrates exploration order | Run step 1 immediately, let script direct you |
| Skipping the Explore agent delegation | Misses broad codebase context | Follow step 1 REQUIRED ACTIONS to delegate |
| Passing empty thoughts to later steps | Loses accumulated context | Include all findings from previous steps |
| Reducing total-steps below 6 | Skips verification and synthesis | Keep minimum 6, increase as script directs |
| Reporting findings without file:line evidence | Unverifiable claims | Always cite specific locations |
Verification
After execution:
- [ ] All priority areas investigated with file-level evidence
- [ ] Findings include severity classification (critical/high/medium/low)
- [ ] Each finding has specific file:line references
- [ ] Synthesis step completed with prioritized recommendations
- [ ] No investigation areas left unexplored from the plan
04 同仓库更多 Skills
validation-authority
Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.
using-brain-memory
Guidance for using Brain semantic memory effectively. Applies Zettelkasten atomic note principles with observations and relations. Use when deciding whether to query or create notes, structuring note content, or understanding the semantic knowledge graph.
threat-modeling
Structured security analysis using OWASP Four-Question Framework and STRIDE methodology. Generates threat matrices with risk ratings, mitigations, and prioritization. Use for attack surface analysis, security architecture review, or when asking what can go wrong.
taste-lints
Custom lints with agent-readable remediation instructions. Enforces taste invariants (file size, naming conventions, structured logging, complexity) and surfaces errors that agents can act on directly. Use when writing or reviewing code to catch style violations early.
style-enforcement
Validate code against style rules from .editorconfig, StyleCop.json, and Directory.Build.props. Detects line ending violations, naming convention issues, indentation problems, and charset mismatches across C#, Python, TypeScript, and JavaScript. Produces JSON reports for pre-commit hooks and CI pipelines.
steering-matcher
Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.