Skip to content
Skills Library
Programming · Review & audit

drift-sync

/drift-sync

Find and resolve drift between intent, contracts, tests, code, and documentation after a change. Use when a task is finished, before a PR, when asked whether things are in sync or what is stale or missing, or when the README, architecture notes, or contracts may no longer match the code.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Find and resolve drift between intent, contracts, tests, code, and documentation after a change. Use when a task is finished, before a PR, when asked whether things are in sync or what is stale or missing, or when the README, architecture notes, or contracts may no longer match the code.

Original author description

Find and resolve drift between intent, contracts, tests, code, and documentation after a change. Use when a task is finished, before a PR, when asked whether things are in sync or what is stale or missing, or when the README, architecture notes, or contracts may no longer match the code.

How it works

  1. Authority order
  2. Process
  3. Scope discipline
Original SKILL.md headings · 49 lines, 337 words
SKILL.md preview
---
name: drift-sync
description: Find and resolve drift between intent, contracts, tests, code, and documentation after a change. Use when a task is finished, before a PR, when asked whether things are in sync or what is stale or missing, or when the README, architecture notes, or contracts may no longer match the code.
---

# Drift Sync

Software drifts: code moves, tests lag, docs go stale, contracts stop describing reality. Drift-sync
compares the artefacts, reports the gaps, and closes them without silently rewriting intent.

## Authority order
1. **User intent** (what they said they want)
2. **Contracts** in `contracts/` (agreed behaviour)
3. **Tests** (executable form of the contract)
4. **Code**
5. **Docs** (README, architecture notes, `CLAUDE.md`)

Lower layers are corrected to match higher ones. If code is right and the contract is wrong, the
**user** decides; you propose, you do not rewrite the contract yourself.

## Process

### 1. Gather
Read the contracts, list the tests, read the diff of the current change, and read the README and any architecture or onboarding notes.

### 2. Compare and classify
| Drift type | Meaning |
| --- | --- |
| Uncovered | A contract clause has no test |
| Orphan | A test or code path matches no clause |
| Contradiction | Code or tests disagree with the contract |
| Stale docs | README, setup steps, or architecture notes no longer match |
| Missing model | A new concept or invariant appeared and is written nowhere |

### 3. Report
Produce a short table: `# | type | where | what is wrong | proposed fix`. Keep it to material
drift. Do not list style nits.

### 4. Resolve
- Uncovered clause: write the test through `outside-in-tdd`.
- Orphan test/code: remove it, or ask whether a clause is missing.
- Contradiction: ask the user which side is right, then fix that side.
- Stale docs and missing model notes: update them now; keep edits minimal and factual.
- Contract edits: show the clause diff and get approval first.

### 5. Close
Run `verify-before-done` on anything you changed, then state: drift found, drift resolved, drift
deliberately left (with reasons).

## Scope discipline
If the user asked for a read-only review or a plan, report drift and change nothing. Reconcile only
within the scope of what the user authorised.

Versions

The database has no other skills named drift-sync.

Database snapshot: 13.11.2026 · package version 48a1cd2b7bb3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100resolve-drift
    Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check…
  • 100update-docs
    Use to keep docs in sync with code. Detects doc-vs-code drift, surfaces stale claims, applies updates. "Update the docs", "docs are out of date", "sync docs to code".
  • 100doncheli-drift
    Detect and reconcile divergence between specs and implementation. Activate when user mentions "drift", "sync", "spec divergence", "out of sync", "spec doesn't match", "implementation differs".
  • 100docs
    Sync docs with code. Updates README, CLAUDE.md or AGENTS.md, docs/, API docs, changelog, ADRs, env examples and agent memory after a change; a drift-check mode reports mismatches without editing. Use when docs are stale, update the docs, sync README, docs out of date, after…
  • 100trove-docs-sync-audit
    Read-only documentation drift audit comparing what the docs claim against what the code does. Covers READMEs, setup guides, API and env docs, changelogs, examples, and generated docs. Use when asked whether docs are stale, missing, or inconsistent after a code change. This is not a code review.
  • 100sync
    Detect Spec-to-Code drift by scanning REQ, DESIGN and TASK specs for references to code that no longer exists, then report it for triage. Use when you say `detect spec drift`, `sync the specs`, or `did my refactor break a spec`, and run it after a hand-edit that moved or deleted…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.