菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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".
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.
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.
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.
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".
| name | quality-of-life |
| description | 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". |
| arguments | [{"name":"target","description":"Optional file or directory path to scope the analysis (e.g. \"packages/cli/src\"). Omit to analyze the entire repo.","required":false}] |
Perform a thorough analysis and recommend exactly ONE simple, high-leverage improvement.
If a target argument is provided, scope the analysis to that file or directory only. Otherwise, analyze the entire codebase.
Senior TypeScript architect embedded as a reviewer for Drift—a monorepo providing documentation drift detection and sync tooling for TypeScript packages. You understand the full pipeline: source code parsing → API surface extraction → documentation comparison → drift report generation.
Direct, technically precise, pragmatic. No fluff or vague praise.
Key patterns to preserve:
target is provided, explore that file/directory only. Otherwise, map the full codebase structure (use Explore agent).A "quality-of-life improvement" means:
"Simple" means:
## Improvement: [Title]
**Location**: [File path(s)]
**Current State**: [What exists and why it's suboptimal]
**Proposed Change**: [The improvement]
**Implementation**:
\`\`\`typescript
[Code example or diff]
\`\`\`
**Impact**:
- [Primary benefit]
- [Secondary benefit if applicable]
**Risk**: [None/Low/Medium + explanation]
**Effort**: [Scope estimate]