agent-sync

Files (1)

• SKILL.md

SKILL.md (first lines)

# Agent Sync

Use the project files as the source of truth. Do not rely on stale chat context.

## Modes

### `/agent-sync check`

Use after an agent switch and before repository-changing work when another AI may have worked since the last sync.

1. Read `AGENTS.md`, `CLAUDE.md` when present, `AGENT_HANDOFF.md`, and the relevant part of `PROJECT_PLAN.md`.
2. Inspect `git status`, recent commits, and diffs. Read files named under **Active Work** or open **Review Ledger** rows.
3. Review the other agent's proposed change or request. Record a concise result in its ledger row: `agree`, `needs change`, `implemented`, or `not applicable`, with the reviewed paths.
4. Update only the current agent's line in **Sync State**. Do not create artificial history entries.
5. Report the actual state succinctly. Do not implement new website work unless the user explicitly authorizes it.

Do not commit, push, stage unrelated files, or erase another agent's uncommitted work during `check`.

### `/agent-sync end`

Use before handing work to the other AI.

1. Run the same reconciliation checks as `check`; resolve or clearly leave open every relevant ledger row.
2. Update **Active Work**, **Next Step**, **Sync State**, and only the handoff details needed by the next agent.
3. Keep `AGENT_HANDOFF.md` compact. The proposing agent removes a resolved ledger row after the other AI's review has been consumed. Non-core resolved notes may be removed immediately; preserve user decisions, active blockers, and one-line delivery history.
4. Verify work in proportion to risk. Stage explicit owned paths only; inspect staged diff; commit and push only when the user has authorized it. Never use `git add -A` in a shared tree.
5. State what remains open and the exact next action.

## Ledger Rules

- Put temporary proposals, review requests, and cross-agent questions in **Review Ledger**, not `AGENTS.md`.
- The agent that created a row owns its deletion after both agents have reviewed it or it is cleanly resolved.
- Move permanent, user-approved constraints to **User Decisions**. Do not delete those without user direction.
- If another agent's changes are unclear, leave the row open and ask rather than guessing.

From shabanakhtar/ai-agent-skills, MIT.

More from shabanakhtar/ai-agent-skills