doc-update

name	doc-update
description	Update project documentation after code changes. Analyzes git diff/PR changes and updates .ai_docs/, project/, and project_doc/ to stay in sync with the codebase. Use after completing a feature, bug fix, or any code changes that affect schemas, contexts, LiveViews, routes, design, or business rules. Triggers on /doc-update or when documentation sync is needed.
argument-hint	[branch-or-commit] (optional, defaults to current branch diff vs main)

Documentation Update Skill

Analyze what changed in the code and update all project documentation to match.

Target: $ARGUMENTS (empty = diff current branch vs main)

Workflow

Step 1: Analyze Changes

Determine what changed:

# If argument is a branch name or empty
git diff main...HEAD --stat
git diff main...HEAD --name-only
git log main..HEAD --oneline

# If argument is a commit hash
git show <commit> --stat

Categorize each changed file:

File Pattern	Category	Docs to Update
lib/heads_up/*.ex (schemas)	Schema change	.ai_docs/4-domains/schemas.md, project_doc/docs/specifications/data-model.md
lib/heads_up/**/contexts or lib/heads_up/{goals,challenges,users}.ex