standards-extractionlisted

# Standards Extraction Skill Extract coding standards, formatting rules, and contribution guidelines from project configuration files. Returns structured data about project conventions. ## Variables | Variable | Default | Description | |----------|---------|-------------| | INCLUDE_LINTER_RULES | true | Parse ESLint, Prettier, Ruff configs | | INCLUDE_EDITOR_CONFIG | true | Parse .editorconfig | | INCLUDE_GIT_HOOKS | true | Check for pre-commit, husky configs | | OUTPUT_FORMAT | json | Output format: json, markdown, or toon | ## Instructions **MANDATORY** - Follow the Workflow steps below in order. Do not skip steps. 1. Check for CONTRIBUTING.md or similar guide files 2. Parse formatting configuration files 3. Parse linting configuration files 4. Check for git hooks and CI checks 5. Compile standards summary ## Red Flags - STOP and Reconsider If you're about to: - Assume formatting rules without checking config files - Skip CONTRIBUTING.md because "it's probably standard" - Infer conventions without evidence from configs - Report rules that contradict actual config files **STOP** -> Read the config files -> Extract actual rules -> Then report ## Workflow ### 1. Discover Standards Files Check for these files (in order): | File | Type | Purpose | |------|------|---------| | `CONTRIBUTING.md` | Markdown | Contribution guidelines | | `CONTRIBUTING` | Text | Contribution guidelines | | `docs/CONTRIBUTING.md` | Markdown | Contribution guidelines | | `.github/CONTRIBUTI