← ClaudeAtlas

codebase-rules-extractorlisted

Extract and document coding rules, patterns, conventions, and anti-patterns from a codebase. Maps the code structure, identifies what to do and what to avoid when creating new code, and generates a comprehensive rules reference document.
Ronnasayd/aipp · ★ 3 · Data & Documents · score 62
Install: claude install-skill Ronnasayd/aipp
MANDATORY: Use explorer-specialist agent (rules mode) for the codebase analysis; write the rules document in the main session MANDATORY: Conduct a comprehensive analysis of the codebase to extract rules and conventions. Your objective is to thoroughly analyze a codebase and extract all coding rules, patterns, conventions, best practices, and anti-patterns that should guide future code creation. ==================== PHASE 1 — CODEBASE DISCOVERY & MAPPING ==================== 1. **Structure Analysis** - Map the directory structure and identify modules/domains - Identify project type(s) (frontend, backend, full-stack, library, etc.) - Document technology stack and frameworks used - List all programming languages present 2. **Documentation Review** - Read ALL markdown files: README.md, docs/SUMMARY.md, design docs, ADRs, RFCs - Check for existing style guides, conventions documents, or coding standards - Identify any .instructions.md, .rules, or similar documentation files - Extract explicit rules already documented 3. **Code Pattern Analysis** - Scan key files from each domain/module - Identify naming conventions (functions, classes, variables, constants) - Analyze code structure patterns (architecture, design patterns used) - Document folder organization and file naming patterns - Identify error handling approaches - Analyze dependency management and import patterns - Study test structure and testing conventions ===============