agentleFS
Sign inStart free
kvantatechkvantatech/RedLine/.github/skills/doc-consistency-check/SKILL.md

doc-consistency-check

Skill1 starsChanged 3 months agoMITView on GitHub

Type: skill (deterministic) · Used by: pre-commit hook · Status: STUB (P0 scaffold — not yet implemented)

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When implemented, run LITERAL checks only over the repo docs: license state wording, MCP phase-of-need wording, .github-canonical path …

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

doc-consistency-check

Pre-commit literal string/path checks that block drift — never a model call in the blocking hook.

Type: skill (deterministic) · Used by: pre-commit hook · Status: STUB (P0 scaffold — not yet implemented)

Prompt

When implemented, run LITERAL checks only over the repo docs: license state wording, MCP phase-of-need wording, .github-canonical path usage, all 5 profiles present, and percentile == p95. Inputs: repo docs -> Output: pass, or a non-zero exit listing the literal violations. Any semantic / paraphrase check is a SEPARATE non-blocking advisory — it MUST NOT be a model call inside the blocking hook.

Tools

none — deterministic (plain code)

Data

  • Reads: repo docs (markdown + config under the repo root)

Notes

Activation: P0. Runs in .githooks/pre-commit; exits non-zero to block the commit. Hard rules: literal string/path matching only in the blocking path — zero model calls; percentile must be p95 everywhere; all 5 profiles must be present. Semantic checks live in a separate advisory, never here.

Frozen skill registry: AGENTS.md in this repo

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free