align-docs
Use when user wants to align docs with the current project status or new discoveries
Best use case
align-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when user wants to align docs with the current project status or new discoveries
Teams using align-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/align-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How align-docs Compares
| Feature / Agent | align-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when user wants to align docs with the current project status or new discoveries
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Align Docs Align all project documentation with actual disk state. ## Principles - Maximize simplicity. Small improvement + ugly complexity = not worth it. - All signal, zero noise. Deduplicate; link to single source of truth. - Agent context files (`AGENTS.md` or `CLAUDE.md`) are cheat sheets. Tables, code snippets, direct statements. Maximize density. ## Execution Checklist ### Step 1: Inventory — diff docs against disk | Check | How | |-------|-----| | **Project structure** (`AGENTS.md`/`CLAUDE.md`) | `ls` root → compare with structure tree | | **Plugin versions** (`AGENTS.md`/`CLAUDE.md`, `MEMORY.md`) | Read each `plugins/*/.claude-plugin/plugin.json` | | **Skills per plugin** (READMEs) | `ls plugins/*/skills/` → compare with skills table | | **Agents per plugin** (READMEs) | `ls plugins/*/agents/` → compare with agents table | | **Shared files** (READMEs) | `ls plugins/*/shared/` → verify architecture matches | | **Conventions & paths** (`AGENTS.md`/`CLAUDE.md`) | Verify every path exists | | **Cross-references** | Check doc links point to existing files | ### Step 2: Fix misalignments | Document | Purpose | What to check | |----------|---------|---------------| | **`AGENTS.md`** (or `CLAUDE.md` if primary) | Project-wide, loaded every conversation | Structure, versions, paths, conventions | | **`MEMORY.md`** | Cross-session memory | Versions, stable facts, iteration numbers | | **Plugin READMEs** | Plugin-specific docs | Skills, agents, architecture, quick start | | **`docs/chronicles/`** | Narrative records | Only if referencing incorrect content | | **Other `docs/`** | Domain docs | Only if stale | ### Step 3: Remove noise - Delete entries referencing nonexistent things - Deduplicate: keep in one place, link from others - Remove empty sections or placeholders
Related Skills
using-development-skills
Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.
update-reqs
Use when user wants to update requirements.in with latest PyPI versions while preserving version patterns
update-reqs-dev
Use when user wants to update requirements-dev.in with latest PyPI versions while preserving version patterns
update-precommit
Use when user wants to update .pre-commit-config.yaml hooks to their latest versions from GitHub
typescript-dev
TypeScript development. Use for TypeScript, Node.js, Express, Fastify, Zod, vitest, jest. Backend, CLI, libraries only — no frontend frameworks.
swift-dev
Swift development. Use for Swift, SwiftUI, UIKit, Vapor, SPM, XCTest, Combine.
staff-review
Use when user wants a code review, deep code review, or staff-level code review of a local branch, repo, directory, or file. Use when user says code review, deep code review, review this branch, review the branch X, review my code, staff review, review locally, or /staff-review.
roast-my-code
Use when user wants a brutally honest code roast, quality critique, or AI-readiness audit. Use when user says roast, roast my code, critique my code, tear apart my code, review quality, or AI-readiness check. Supports --fix flag to auto-fix CRITICAL and HIGH issues via core-dev workflow.
resolve-merge
Use when the user asks to resolve merge conflicts, fix a failed merge, rebase conflict, or run /resolve-merge. Use when git status shows UU/AA/DD conflicts, when there are <<<<<<< conflict markers, when git merge or git pull failed with CONFLICT, or when numbered docs/plans need renumbering after merge. Triggers on: merge conflict, conflict markers, both modified, git merge failed, rebase conflict, resolve conflicts.
python-dev
Python development. Use for Python, FastAPI, Pydantic, asyncpg, pytest, pandas, SQLAlchemy.
produce-feedback
Use when user wants to produce a factual chronicle of development-skills plugin interactions in the current conversation for later ingestion, or runs /produce-feedback. Pure record, no judgment.
java-dev
Java development. Use for Java, Spring Boot, Maven, Gradle, JPA, Hibernate.