standards-extraction

Extract coding standards and contribution guidelines from project configuration files.

8|1|Updated Jul 11, 2025

Search Tags:#onboarding #standards #editorconfig #lint-config #config-extraction #CONTRIBUTING.md

Ready to run

npx skills add https://github.com/Consiliency/treesitter-chunker --skill standards-extraction

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standards-extraction
Source: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/standards-extraction
Command: npx skills add https://github.com/Consiliency/treesitter-chunker --skill standards-extraction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies coding standards and contribution guidelines within a project by scanning configuration files and guidelines, enabling consistent onboarding and contributor expectations.

Core Features & Use Cases

Discovery of contribution guidelines from CONTRIBUTING.md and related files
Extraction and summarization of formatting and linting rules from editorconfig, Prettier/ESLint/ruff configs, and pre-commit hooks
Onboarding aid: auto-generated standards summaries for teams and new contributors

Quick Start

Run the standards-extraction skill against a repository containing CONTRIBUTING.md, .editorconfig, and lint configs to produce a structured standards report.

Frequently Asked Questions about standards-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract coding standards from my project's configuration files?▼

Extract coding standards by scanning CONTRIBUTING.md, .editorconfig, .prettierrc, ESLint/ruff configs, and pre-commit hooks to produce a structured report surfacing formatting, linting, and CI rules for your team.

Can I automatically summarize contribution guidelines for new team members?▼

Yes. Parse your repository's contribution guidelines and configuration files to generate machine-readable standards summaries that help onboard contributors with clear commit, formatting, and CI expectations.

What configuration files does standards extraction support?▼

Standards extraction parses CONTRIBUTING.md, .editorconfig, .prettierrc, ESLint configs, ruff configs, and pre-commit settings to identify and summarize coding conventions and contribution rules.

How do I ensure project conventions are consistent across my team?▼

Identify and centralize all coding standards from your lint configs, editor configurations, and contribution docs into a single structured report that everyone can reference during development.

Do I need specific tools installed to extract lint and formatting rules?▼

No prerequisites beyond having CONTRIBUTING.md and configuration files present in your repository. The Skill parses existing .editorconfig, linter configs, and pre-commit hooks without additional setup.

Why should I document standards extracted from config files?▼

Explicit standards reduce onboarding friction, prevent CI failures from missed conventions, and align distributed teams on formatting and commit practices embedded in your project's configuration.