agentleFS
owenpkentowenpkent/deckhand/.claude/skills/sync-check/SKILL.md

sync-check

Skill1 starsChanged 4 months agoMITView on GitHub

Walk the Deckhand change-propagation table for a pending

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. databricks/app-templates★ 222same name
    2. ItamarZand88/CLI-Anything-WEB★ 215same name
    3. vericontext/vibeframe★ 185same name
    4. tonydzi/second-brain-starter-kit★ 6same name

    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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    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. Distinctive:

    Read the table from the file each time.

    line 38
  2. Very specific:

    Verify every relative link and anchor the change added resolves to a real file and heading.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Sync check

Deckhand's spec is spread across files that must move together. This walks the table so nothing lands half-updated.

Steps

  1. git diff --stat main...HEAD and git status --short to get the changed set. If nothing is staged or committed, ask which change to check rather than guessing.
  2. Classify the change against the rows of docs/WORKFLOW.md section 2. A change can match more than one row. If it matches none, say so and propose the new row rather than inventing an ad hoc rule.
  3. For every "Yes" cell in the matched rows, check whether that file is in the changed set. The nine columns, in table order:

    ColumnFile
    CMdocs/CONTROL_MAPPING.md
    UIdocs/UI_SPEC.md
    APdocs/ADAPTER_PROTOCOL.md
    CCAdocs/CLAUDE_CODE_ADAPTER.md
    ARCHdocs/ARCHITECTURE.md
    SMdocs/SECURITY_MODEL.md
    A11Ydocs/ACCESSIBILITY.md
    DECdocs/DECISIONS.md
    CHGCHANGELOG.md

    Read the table from the file each time. It has grown before and the column set is not frozen. CHG is "Yes" in every row today, so a docs change with no changelog entry is always a finding.

  4. Separately check TODO.md and ROADMAP.md: they are not columns, but update them if the change opens or closes a tracked item. Also check docs/EXECUTIVE_SUMMARY.md, which is derived and never authoritative but drifts first when a frozen concept moves.
  5. Guard rails, report a failure if any is broken:
    • ADR-006: the approval path fails to ask, never to allow. Any touch here must update docs/SECURITY_MODEL.md in the same change.
    • ADR-008: the six status colours and meanings are frozen. unknown is the only Deckhand addition. No new states, no repurposed colours.
    • docs/ACCESSIBILITY.md rules are requirements: no required holds, drags, double-clicks, hovers, or keyboard; 44 px minimum targets.
    • Claude Code integration facts carry a partial verification stamp only. Four things are observed against 2.1.220; everything else is documented or unverified and keeps its hedge unless the stamp in docs/CLAUDE_CODE_ADAPTER.md was upgraded in this same change.
    • Status lines are never upgraded without the evidence that justifies it.
    • ADRs are append-only. A superseded decision gets a new entry and a marker, never an edited one.
  6. Run powershell -NoProfile -File scripts/check-docs.ps1 -All (no pwsh on this machine; CI uses pwsh) and confirm it exits 0. That script is where the dash, status line, ADR numbering, and Constellation rules live; do not restate them here.
  7. Verify every relative link and anchor the change added resolves to a real file and heading. lychee is not installed locally, so this is an approximation of the CI link job, not the same check.

Output

A table of file, required (yes/no), touched (yes/no), verdict. Then a short list of concrete edits still owed. Do not make the edits unless asked.

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.