Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bjornmelin avatar

Docs Align

  • 6 installs
  • 5 repo stars
  • Updated August 5, 2026
  • bjornmelin/dev-skills

docs-align is a skill that detects documentation drift after implementation and updates ADRs, specs, README, and AGENTS files.

About

This skill aligns documentation with code by detecting drift after implementation work. Developers use it to update ADRs, specs, README, and AGENTS files based on what changed in the code. It runs a drift-collection script, compares against docs, and produces a gap map of doc tasks rather than editing blindly.

  • Detects documentation drift after implementation and updates ADRs, specs, README, AGENTS
  • Produces a gap map of missing, update, and delete doc tasks
  • Includes a docs_drift collect/compare/render script pipeline

Docs Align by the numbers

  • 6 all-time installs (skills.sh)
  • Ranked #1,205 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

docs-align capabilities & compatibility

Capabilities
documentation
Use cases
documentation
From the docs

What docs-align says it does

Use this skill after implementation work or when you suspect documentation drift.
SKILL.md
Create or update an ADR when the implementation changed:
SKILL.md
The task is only code review remediation.
SKILL.md
npx skills add https://github.com/bjornmelin/dev-skills --skill docs-align

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs6
repo stars5
Last updatedAugust 5, 2026
Repositorybjornmelin/dev-skills

What it does

Detecting documentation drift after implementation and updating ADRs, specs, README, or AGENTS files to match the code.

Who is it for?

Developers reconciling documentation with code after an implementation change.

Skip if: Code-review remediation or dependency planning; the docs say do not use for those.

When should I use this skill?

After implementation work or when you suspect documentation drift.

By the numbers

  • 4-step collect/compare/render/update workflow

Files

SKILL.mdMarkdownGitHub ↗

Docs Align

Use this skill after implementation work or when you suspect documentation drift.

Workflow

1. Read the repo AGENTS.md. 2. From this skill root (directory containing SKILL.md), run drift collection (requires git on PATH):

  • python3 scripts/docs_drift.py collect --cwd <repo> --out <json>
  • Equivalent collect-only shortcut: python3 scripts/check_docs_drift.py --cwd <repo> --out <json>

3. python3 scripts/docs_drift.py compare --input <json> --out <json> 4. Render the summary:

  • python3 scripts/docs_drift.py render --input <json> --format md

5. Use Alignment policies below only for doc surfaces that the gap map says are in scope. 6. Update docs only after the gap map is clear.

Path note

Commands above assume the current working directory is this skill’s root (skills/docs-align in this repository). If the working directory is elsewhere, invoke the same files with an absolute path, for example:

python3 /path/to/docs-align/scripts/docs_drift.py collect --cwd <repo> --out <json>

Alignment policies

ADR

Create or update an ADR when the implementation changed:

  • architecture boundaries
  • execution model
  • durable workflow policy
  • major dependencies or infrastructure choices

Do not create ADR churn for small local refactors.

Spec

Update product or architecture specs when the implementation changed:

  • interfaces
  • contracts
  • verification steps
  • operational behavior

Prefer deleting stale spec text over leaving contradictory guidance.

README

Update the README when the change affects:

  • setup
  • commands
  • environment variables
  • high-level architecture or usage expectations

Keep the README high signal; move deep details into docs when needed.

Use When

  • The task is post-implementation doc alignment.
  • The user wants README, ADR, spec, or AGENTS updates based on code changes.

Do Not Use When

  • The task is only code review remediation.
  • The task is only dependency planning.

Outputs

  • likely impacted docs
  • missing/update/delete doc tasks
  • a concise docs alignment summary

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.