AnotherSava

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.

Remove dead code, fix duplication, and optimize imports in modified files

Configure deployment script and run it, verifying it succeeds

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

Update stale documentation and comments to match current code

List your GitHub-owned local clones under PROJECTS_ROOT that have pending work (uncommitted changes, unpushed commits, or inbound remote commits), with branch, counts, age of oldest pending work, and a per-repo summary. Each run fetches every repo's origin in parallel so the counts reflect the current remote. TRIGGER when: user asks "/github-status", wants a cross-project overview of their repos,

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

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

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

Prepare commits for the current feature branch, push, and create or update a PR to main.

Merge a PR locally with fast-forward to preserve GPG-signed commits, then clean up.

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

Extract and persist conversation learnings before context loss. TRIGGER when: user runs /reflect, or before /clear or compaction.

Tag a new version, push to trigger CI, monitor the build, and verify the GitHub release

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

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.

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

Analyzes changes and generates Conventional Commit messages