AnotherSava

Create or update the data flow architecture document (docs/pages/data-flow.md).

Update stale documentation and comments to match current code

Analyze progress log, commits, and optionally a plan to summarize what was done, what diverged, and what review found.

Soft-reset unpushed commits back into the working tree for re-committing

Annotate any file in Plannotator's browser UI. Markdown and HTML files are passed through directly; other files are wrapped in a temporary `.md` with a fenced code block, annotated, then the temp file is deleted.

Analyzes changes and generates Conventional Commit messages

Complete Claude Code environment: global guidelines, skills, hooks, settings, version-controlled memory and learnings, and shared git config

Force-update the plannotator plugin by nuking stale caches and reinstalling fresh

Arrange a project's README and GitHub Pages documentation into a consistent user-first layout: short README that links out, just-the-docs Jekyll site with a user-facing index, one page per user-facing feature (split into child pages when long), and a developer guide with technical sub-pages. TRIGGER when: setting up docs/ for a new project, adding a GitHub Pages site, writing or restructuring a RE

Configure deployment script and run it, verifying it succeeds

Create an implementation plan for a new feature, refactor, or fix. Guides an interactive design discussion and produces a structured plan document.

Guidelines for creating and updating Claude Code skills. TRIGGER when: writing a new SKILL.md, modifying an existing skill, or the user asks about skill conventions.