AnotherSava
UserComplete Claude Code environment: global guidelines, skills, hooks, settings, version-controlled memory and learnings, and shared git config
Categories
Indexed Skills (19)
clean-code
Remove dead code, fix duplication, enforce naming conventions, and optimize imports in modified files
commit
Reflects on the session, then analyzes changes and generates Conventional Commit messages
deploy
Configure deployment script and run it, verifying it succeeds
document-data-flow
Create or update the data flow architecture document (docs/pages/data-flow.md).
documentation
Update stale documentation and comments to match current code
github-status
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, "which repos have unpushed commits", "what's new on remotes", or "what have I been working on". DO NOT TRIGGER when: user is asking about a single specific repo (use `git status` / `git log` directly).
plan-ralphex
Create an implementation plan for a new feature, refactor, or fix. Guides an interactive design discussion and produces a structured plan document.
pr-create
Prepare commits for the current feature branch, push, and create or update a PR to main.
pr-merge
Merge a PR locally with fast-forward to preserve GPG-signed commits, then clean up.
pr-prepare
Analyze progress log, commits, and optionally a plan to summarize what was done, what diverged, and what review found.
reflect
Extract and persist conversation learnings before context loss. TRIGGER when: user runs /reflect, or before /clear or compaction.
release
Tag a new version, push to trigger CI, monitor the build, and verify the GitHub release
github-pages
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 README that will link to GH Pages, adding a new user-facing feature page, or asked to align docs with this project or bga-assistant. DO NOT TRIGGER when: editing unrelated docs outside docs/, working on a project that already has an incompatible docs framework (Docusaurus, MkDocs, VitePress, etc.).
publish-chrome-extension
Republish a new release of an existing Chrome extension to the Chrome Web Store: downloads the release zip from GitHub, reviews the tracked store-listing info for staleness, uploads the zip via the Web Store API, and submits it for review. TRIGGER when: the user wants to publish, republish, or upload a new extension version to the Chrome Web Store, typically right after /release. DO NOT TRIGGER when: creating a brand-new store listing, editing store listing content (description, screenshots), or building/tagging a release (use /release for that).
build
Configure build script and run it
plannotator-update
Force-update the plannotator plugin by nuking stale caches and reinstalling fresh
reset
Soft-reset unpushed commits back into the working tree for re-committing
annotate
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.
skill
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.