Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

drift-fix

Sterne4

Forks0

Aktualisiert19. Juli 2026 um 00:35

Fix documentation drift reported by drift scan/lint — stale signatures, wrong parameter names/types, references to removed or renamed exports, prose drift in markdown. Use after `drift scan` or `drift lint` reports issues, or when asked to "fix drift", "fix the docs", "sync docs to the API". Edits docs to match the API, never the reverse.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

ryanwaits

ryanwaits/drift

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	drift-fix
description	Fix documentation drift reported by drift scan/lint — stale signatures, wrong parameter names/types, references to removed or renamed exports, prose drift in markdown. Use after `drift scan` or `drift lint` reports issues, or when asked to "fix drift", "fix the docs", "sync docs to the API". Edits docs to match the API, never the reverse.

Drift Fix: Make Docs Match Reality

Fix every issue drift lint reports, verifying each correction against the truth oracle. Docs move toward the API — never edit code to match docs unless the user says the docs are the intent.

Loop

drift lint --json (add --spec/--abi/--docs truth flags as needed) → issues with filePath + line.
For each issue:
- drift get <export> --json → the authoritative signature/params/deprecation.
- Edit the doc (or JSDoc) at filePath:line to match. Only touch code references, signatures, parameter tables, and factual claims — preserve the prose voice around them.
- Unknown/removed export referenced in docs? drift list <name> --json for the closest current name; if it was renamed, update the reference; if truly removed, delete or rewrite the claim.
Re-run drift lint --json until count is 0.
Report: issues fixed (with file:line), issues intentionally left (with reason).

Rules

One drift get per claim you rewrite — never from memory.
Never invent parameter descriptions; copy meaning from the spec's descriptions or leave the existing prose.
Deprecated export documented as current? Point docs at the replacement (drift get shows deprecation reason) and mark the old form deprecated — don't silently delete.
Exit codes: 0 clean, 1 findings, 2 tool error. A persistent 2 means fix the invocation, not the docs.

Mehr aus diesem Repository

gleiches Repository

drift

ryanwaits/drift

Documentation drift detection and sync for any API surface — TypeScript packages, OpenAPI/REST specs, Clarity contracts. Use when checking doc coverage, validating docs against an API, detecting drift, or fixing outdated documentation. Triggers on "doc coverage", "validate docs", "drift", "docs out of sync", "are my docs accurate", "update docs to match API".

2026-07-194

drift-docs-map

ryanwaits/drift

Bootstrap and maintain a drift docs map — the committed page→type artifact for docs key-coverage mode (drift scan --docs-map). Use when setting up key-coverage for a docs site, mapping docs pages to spec types, classifying ambiguous option keys, or when asked to "set up docs coverage", "map docs pages to types", "bootstrap the docs map". The agent proposes; the human commits; CI runs the map deterministically.

2026-07-194

drift-enrich

ryanwaits/drift

Document undocumented API surface found by drift — generate signature-accurate JSDoc/doc stubs for exports that lack documentation. Use after `drift scan`/`drift coverage` reports undocumented exports, or when asked to "improve doc coverage", "document the API", "add missing docs". Produces stubs with TODO prose markers, never invented descriptions.

2026-07-194

docs-verify

ryanwaits/drift

Verify an entire docs site/directory against the real API surface using drift as the truth oracle. Use when asked to audit docs accuracy, check hand-written guides against an OpenAPI spec or TypeScript package, find stale/phantom documentation, or produce a docs-drift report. Triggers on "verify the docs", "audit docs against the API", "are these guides accurate", "docs drift report".

2026-07-094

quality-of-life

ryanwaits/drift

Analyze the Drift codebase and identify exactly ONE high-leverage, low-risk quality-of-life improvement. Use when: user runs "/quality-of-life", asks for "a quick win", "something to improve", "code quality check", or "what should I clean up next".

2026-02-124

name	drift-fix
description	Fix documentation drift reported by drift scan/lint — stale signatures, wrong parameter names/types, references to removed or renamed exports, prose drift in markdown. Use after `drift scan` or `drift lint` reports issues, or when asked to "fix drift", "fix the docs", "sync docs to the API". Edits docs to match the API, never the reverse.

Drift Fix: Make Docs Match Reality

Fix every issue drift lint reports, verifying each correction against the truth oracle. Docs move toward the API — never edit code to match docs unless the user says the docs are the intent.

Loop

drift lint --json (add --spec/--abi/--docs truth flags as needed) → issues with filePath + line.
For each issue:
- drift get <export> --json → the authoritative signature/params/deprecation.
- Edit the doc (or JSDoc) at filePath:line to match. Only touch code references, signatures, parameter tables, and factual claims — preserve the prose voice around them.
- Unknown/removed export referenced in docs? drift list <name> --json for the closest current name; if it was renamed, update the reference; if truly removed, delete or rewrite the claim.
Re-run drift lint --json until count is 0.
Report: issues fixed (with file:line), issues intentionally left (with reason).

Rules

One drift get per claim you rewrite — never from memory.
Never invent parameter descriptions; copy meaning from the spec's descriptions or leave the existing prose.
Deprecated export documented as current? Point docs at the replacement (drift get shows deprecation reason) and mark the old form deprecated — don't silently delete.
Exit codes: 0 clean, 1 findings, 2 tool error. A persistent 2 means fix the invocation, not the docs.