# Extract Repository Coding Standards

Repository conventions are often scattered across guides, formatter settings, linter rules, hooks, and CI files. This skill consolidates those sources into one evidence-based standards summary.

## Install

```bash
npx skillstore add consiliency/standards-extraction
```

## Metadata

- Status: approved
- Slug: consiliency-standards-extraction
- Skillstore revision: r1
- Version status: missing
- Tree hash: 88ce9d81ed2cfeee33bb6b9aa3d319a80045b45db430f62608cd2f36dbbf9c53
- Author: Consiliency
- GitHub username: Consiliency
- License: MIT
- Repository: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/standards-extraction
- Ref: 635f69fb8d2f4e6330ba47a4e5a0fb239c04d110
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/consiliency-standards-extraction
- Manifest: https://skillstore.pages.dev/api/skills/consiliency-standards-extraction/manifest

## Capabilities

- Discovers contribution guides, EditorConfig files, formatter settings, linter configurations, hooks, templates, and CI workflows.
- Extracts commit formats, branch naming rules, pull request requirements, testing expectations, and explicit code style guidance.
- Summarizes indentation, line endings, line length, quote style, semicolon usage, and other formatter settings.
- Identifies enabled linter rules, disabled rules, extended configurations, and custom rules across supported ecosystems.
- Reports pre-commit, pre-push, lint, test, and build checks with their source files.
- Produces structured JSON, Markdown, or TOON summaries based on the requested output format.

## Use Cases

- Prepare Developer Onboarding: Create a concise standards guide before a developer begins work in an unfamiliar repository.
- Review Contribution Requirements: Collect commit, branch, pull request, test, formatting, and linting requirements before submitting changes.
- Align Automated Work: Give coding agents a sourced convention summary before they modify code or prepare pull requests.

## Prompt Templates

### Extract Basic Standards

```
Inspect this repository and summarize its contribution, formatting, and linting standards. Cite the source file for each rule.
```

### Create an Onboarding Guide

```
Extract repository standards and present a Markdown onboarding checklist covering setup, commits, branches, formatting, linting, tests, and pull requests.
```

### Compare Configuration Sources

```
Analyze all standards files, identify conflicting rules, explain likely precedence, and separate explicit requirements from inferred conventions.
```

### Build an Automation Profile

```
Produce a structured standards profile for an AI coding workflow. Include source evidence, confidence, conflicts, hooks, CI gates, and unresolved decisions.
```

## Limitations

- Results depend on configuration and guidance files available in the repository.
- The skill summarizes declared standards but does not verify that source code follows them.
- Conflicting configuration files require user or maintainer judgment to establish precedence.
- The referenced config-parsing cookbook recipe is not included in this package.

## Best Practices

- Require a source file for every reported convention.
- Separate explicit rules from inferred patterns and unresolved conflicts.
- Review contribution guides before interpreting tool configuration.

## Anti Patterns

- Do not assume common defaults when configuration evidence is absent.
- Do not merge conflicting rules without reporting their sources.
- Do not present example values from the skill as repository findings.

## Security Audit

- Audited at: 2026-07-13T17:28:03.922\+00:00
- Summary: All 36 external-command findings are Markdown code spans or fences that document filenames, configuration examples, and integration names; they do not execute commands. The URL is a JSON Schema identifier, not a network request, and no malicious semantic behavior was found.

## Stats

- Views: 257
- Downloads: 10
- Favorites: 0
- Popularity score: 0