agentleFS
expoexpo/exact/.claude/skills/llp-maintain/SKILL.md

llp-maintain

Skill4.3k starsChanged 3 days agoMITView on GitHub

Keep an LLP corpus in sync with its code. Detects code/doc drift, validates @ref annotations interactively, checks provenance tags, and proposes reconciliations, ref repairs, status changes, and overlay changes. Modes — pre-pr, audit, reconcile, retire-proposal, curate (the promote → archive → realign pass). Proposes; never applies.

2 other projects use a version of this, 1 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 8 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the expo/exact repository that our weekly crawl found: only 8 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about expo/exact

The biggest 5 of 8 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 8
  • Other versions2 projects use a version of this.

    Word for word · 1

    1. expo/expo-device-hub★ 285100% same

    Edited · 1

    1. peterpme/skills★ 2892% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Before opening a PR (pre-pr, the common case).

    line 19
  2. Distinctive:

    MUST propose, never apply: no edit, ref repair, or status change without sign-off.

    line 23
  3. Very specific:

    MUST NOT classify untagged rationale claims silently — flag them for the author to mark [observed]/[confirmed]/[inferred].

    line 24
  4. Very specific:

    MUST NOT claim to be a CI gate.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

llp-maintain

<!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0004-design-principles.principles.md — co-evolution and living documents, the model this operationalizes --><!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0000-linked-literate-programming.explainer.md#6-validation-ref-check — the deterministic subset lives in ref-check, not here --><!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0011.000-curation-pass.guide.md — the curate intent follows this procedure -->

The upkeep engine. Living documents rot into misleading guidance unless code and docs co-evolve; this skill finds the drift and proposes fixes. The propose-only line is what lets one skill cover four maintenance moments without becoming a mega-skill.

Invoke as /llp-maintain --intent <pre-pr | audit | reconcile | retire-proposal | curate> (each has a sensible default scope).

Trigger

Before opening a PR (pre-pr, the common case); periodically or on suspicion (audit); after a pull or against a branch (reconcile); "this doc looks done/stale" (retire-proposal); after design work lands, before a release, or on cadence (curate).

Invariants

  • MUST propose, never apply: no edit, ref repair, or status change without sign-off. Output is a reviewable checklist or diff, never a mass rewrite.
  • MUST NOT classify untagged rationale claims silently — flag them for the author to mark [observed]/[confirmed]/[inferred].
  • curate MUST run its three verbs in order — promote, archive, realign — and MUST realign the code only against llp/foundation/, never against the whole corpus. Promotion proposals MUST apply LLP 0000's admission test (design recreatable from the set; set-level; too-small fails), not importance.
  • MUST NOT claim to be a CI gate. The deterministic, merge-blocking checks are ref-check's job; this skill is the interactive, judgment-bearing complement.

Checks

For @refs in scope: broken target/anchor (error — list the anchors that do exist); tombstoned/superseded target (warning, note the replacement); stale gloss (hint); orphaned annotation whose attached construct is gone (warning). For provenance-tagged docs: [inferred] in Accepted/Active (error); [observed] without a stated location, or [confirmed] without name+date (flag for the author). For installed skills: a source: pin that lags upstream releases (note, when network allows). Beyond the mechanical: code whose behavior no longer matches the section it references; new files implementing a documented LLP with no @ref; LLP sections the diff contradicts.

Modes

IntentDefault scopeArtifact
pre-prworking treeco-evolution checklist ("update doc or code" / "repair ref" / "consider annotating") + proposed status changes, not applied
auditcorpusfindings list: drift, broken refs, stale statuses
reconcilediff range / branchper-doc reconciliation proposals (or "the code drifted, not the doc")
retire-proposalone named doca drafted Superseded/Tombstoned proposal with rationale (a status change in the header — files never move)
curateoverlays + foundation vs. codethe PROMOTE / ARCHIVE / REALIGN checklist of LLP 0011.000: links to add or remove, folds, status fixes, and code changes foundation now demands

Hand-offs

  • A reconciliation that is really a new design decision → llp-review.
  • Broken refs surfaced by llp-orient land here for repair proposals.
  • A stale source: pin noted by audit → /llp-adopt update applies the update after an approved diff (this skill never applies).
  • Deterministic CI enforcement → ref-check.

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.