standards-discovery

# Standards Discovery - Project Documentation Scanner Discovers and parses project-specific coding standards, style guides, and architecture documentation to ensure code reviews align with project conventions. --- ## Purpose Before reviewing code, understand what standards the project follows: - Naming conventions - Architecture patterns - Testing requirements - Import rules - Code organization **Project-specific rules always override generic best practices.** --- ## Discovery Workflow ### Step 1: Search for Standards Files **ALWAYS run these searches first:** ```bash # Primary standards files find . -type f \( \ -iname "CONTRIBUTING*" -o \ -iname "CODING*STANDARD*" -o \ -iname "STYLE*GUIDE*" -o \ -iname "CODE*STYLE*" -o \ -iname "CONVENTIONS*" -o \ -iname "ARCHITECTURE*" -o \ -iname "GUIDELINES*" -o \ -iname "DEVELOPMENT*" -o \ -iname "STANDARDS*" \ \) -not -path "./.git/*" -not -path "./node_modules/*" -not -path "./.venv/*" -not -path "./vendor/*" 2>/dev/null # Check docs directory find ./docs -type f -name "*.md" 2>/dev/null # Check .github directory find ./.github -type f -name "*.md" 2>/dev/null ``` ### Step 2: Check Common Locations | Location | Priority | What to look for | |----------|----------|------------------| | `CONTRIBUTING.md` | HIGH | Code style, PR process, testing requirements | | `docs/ARCHITECTURE.md` | HIGH | Layer structure, patterns used | | `docs/CODING_STANDARDS.md` | HIGH | Naming, formatting, imports | | `.github/C...