Run any Skill in Manus with one click

drift-enrich

Stars4

Forks0

UpdatedJuly 19, 2026 at 00:35

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ryanwaits

ryanwaits/drift

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	drift-enrich
description	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.

Drift Enrich: Document the Undocumented

Raise coverage by adding signature-accurate documentation for exports drift reports as undocumented. Structure comes from the spec; prose meaning comes from the human.

Loop

drift list --undocumented --json (add --spec/--abi truth flags as needed) → the backlog.
For each export:
- drift get <name> --json → params (names, types, required), returns, deprecation.
- Write the doc/JSDoc stub: every param listed with its real type and optionality, return shape stated, deprecation carried over.
- Where the spec has a description, use it. Where it doesn't, insert  (markdown) or TODO: (JSDoc) — never invent behavior.
drift coverage --json to confirm the score moved.
Report: exports documented, TODOs left for the human, before/after coverage.

Rules

Signatures from drift get only — never from reading source or memory.
A stub with an honest TODO beats a confident hallucination; wrong prose is drift you just created.
Match the file's existing doc conventions (JSDoc tags used, table formats) before adding new ones.
Skip exports tagged @internal unless the user asks.

More from this repository

same 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-fix

ryanwaits/drift

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.

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-enrich
description	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.

Drift Enrich: Document the Undocumented

Raise coverage by adding signature-accurate documentation for exports drift reports as undocumented. Structure comes from the spec; prose meaning comes from the human.

Loop

drift list --undocumented --json (add --spec/--abi truth flags as needed) → the backlog.
For each export:
- drift get <name> --json → params (names, types, required), returns, deprecation.
- Write the doc/JSDoc stub: every param listed with its real type and optionality, return shape stated, deprecation carried over.
- Where the spec has a description, use it. Where it doesn't, insert  (markdown) or TODO: (JSDoc) — never invent behavior.
drift coverage --json to confirm the score moved.
Report: exports documented, TODOs left for the human, before/after coverage.

Rules

Signatures from drift get only — never from reading source or memory.
A stub with an honest TODO beats a confident hallucination; wrong prose is drift you just created.
Match the file's existing doc conventions (JSDoc tags used, table formats) before adding new ones.
Skip exports tagged @internal unless the user asks.