agentleFS
kapadiaskapadias/nonna/.claude/skills/sync/SKILL.md

sync

Skill0 starsChanged 46 days agoMITView on GitHub

Reconcile drift across the five mirrors — issue tracker, docs/STATUS, git/PR, the .claude harness, and memory — so every record of the system agrees.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use develop, scope and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

  • Harut8Skill

    architect

    Also in 6 projects that use this

The file

Files
SKILL.md

@docs/STATUS.md

Reconcile the five mirrors for: $ARGUMENTS (if empty, the current branch's work).

Steps

Walk the five-mirror Definition of Done (full checklist: .claude/rules/sync.md) and fix any drift:

  1. Tracker — issue in the right status, PR linked?
  2. Docs — docs/STATUS.md current? Usage changed → README/docs updated? Non-trivial decision made → /adr filed?
  3. Git / PR — branch + PR open, targeting develop, linked to the issue?
  4. Harness — any agent/skill/command/rule/hook changed? → .claude/README.md and CLAUDE.md updated?
  5. Memory — durable decisions (the why, rejected alternatives, learned invariants) captured to survive a context reset?
  6. Tests — suite green? A task is never done in any mirror while tests are red.
  7. Debt ledger — run bash $NONNA/skills/lean/scripts/check-debt.sh --ledger ($NONNA = the harness root announced at SessionStart). The ledger is part of the docs mirror: a no-trigger marker is drift — name its trigger or delete the corner.

Output

A short report: each mirror marked ✅ in-sync or ✗ drifted-then-fixed, the ledger summary line, and anything that still needs a human decision. Never leave one mirror claiming "done" while another contradicts it.

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.