Coding Standards Skill Reference

extracting-coding-standards

The extracting-coding-standards skill turns a repo’s conventions into registered rules and canonical snippets, then renders the version-stamped ## Coding Standards section in CLAUDE.md or AGENTS.md.

Skill contract

Field	Value
Slug	`extracting-coding-standards`
Purpose	Turn a repo’s coding intent into registered rules and snippets, then render the ambient standards section.
When to use	First-time setup, re-extraction after a convention shift, or adding snippet coverage for a pattern the library missed.
When not to use	Checking registered standards, consulting snippets while writing, or deriving style rules without registering them.

Triggers

The skill uses these trigger phrases:

Trigger phrase	What it means
`extract our coding standards`	Set up Coding Standards from the repository’s source evidence.
`derive rules and snippets from this repo`	Build the registered rules and canonical snippets from source material.
`register our coding conventions with gloria`	Register the conventions in the standards library.
`set up the standards library`	Create the library and prepare it for rendering.

Outputs

Registered rules and canonical snippets, with approval before anything lands in the library.
A version-stamped ## Coding Standards section in CLAUDE.md or AGENTS.md.

using-coding-standards

The using-coding-standards skill keeps write-time code aligned with the registered standards library. It looks up the canonical snippet before pattern-shaped code and leaves provenance markers on adopted or adapted code so reuse stays visible.

Skill contract

Field	Value
Slug	`using-coding-standards`
Purpose	Consult the snippet library before writing pattern-shaped code, then keep reuse visible with provenance markers.
When to use	Before writing pattern-shaped code, when the repo already has a registered Coding Standards library, and when `CLAUDE.md` or `AGENTS.md` already includes `## Coding Standards`.
When not to use	One-off logic, repos with no registered standards, or extraction and checking tasks.

Triggers

The skill responds to prompts such as:

Trigger phrase	What it means
`Before you write that DAO, check our coding standards for a snippet.`	Look up the matching canonical snippet before writing.
`consult the snippet library before writing pattern-shaped code`	Search the registered library before starting a repeating shape.
`before writing pattern-shaped code`	Run the snippet lookup before the first line.

Outputs

Adopted or adapted code that keeps the canonical exemplar shape.
gloria:snippet provenance markers that show which project and snippet id the code came from.

checking-coding-standards

The checking-coding-standards skill compares code with the registered rules and snippet library, then writes drift findings to the ledger. It stays read-only, so it never edits source.

Skill contract

Field	Value
Slug	`checking-coding-standards`
Purpose	Evaluate code against registered rules and snippets, then report drift to the ledger.
When to use	PR or branch review, a periodic or on-demand full audit, or any check invocation.
When not to use	Fixing violations or checking repos with no registered standards.

Triggers

The skill uses these trigger phrases:

Trigger phrase	What it means
`check this PR against our standards`	Run a diff-scoped standards check.
`run a standards check`	Evaluate the current code against the registered standards.
`audit the repo for drift`	Run a full audit and look for broader drift.
`has our code drifted from the rules`	Compare the code against the registered rules and snippets.

Outputs

Drift findings written to the ledger, with file and line detail where needed.
Clean runs still resolve open findings in scope and refresh the record.
Read-only results that report findings without changing code.