AnotherSava
UserComplete Claude Code environment: global guidelines, skills, hooks, settings, version-controlled memory and learnings, and shared git config
Categories
Indexed Skills (37)
documentation
Update stale documentation and comments to match current code
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.).
commit
Reflects on the session, then analyzes changes and generates Conventional Commit messages
publish-chrome-extension
Republish a new release of an existing Chrome extension to the Chrome Web Store: downloads the release zip from GitHub, checks what changed since the version the store already holds, 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).
transcrypt
Encrypt files in a git repo with transcrypt using the shared Doppler-stored passphrase, or unlock (decrypt) an already-encrypted repo after a fresh clone. Designated files stay plaintext in the working tree but are stored encrypted in git history. TRIGGER when: the user wants to commit a file encrypted, protect a sensitive committed doc, set up transcrypt in a repo, or decrypt/unlock secret files after cloning. DO NOT TRIGGER when: the secret is an env-style credential (API key, token, password) that belongs in Doppler/`.env`, not a committed file.
publish
Configure and run PUBLISH — ship a project outward to where its users are. The counterpart to `deploy`, which only makes code runnable on this machine. Writes `config/publish.env` and a per-machine `scripts/publish.sh` wrapper, then publishes and verifies the live result. Owns the WHOLE configuration path, including what a co-tenant on a shared host must obtain from the `landlord` repo before its first publish can work (§2). TRIGGER when: the user explicitly runs /publish or asks to set up publishing for a project. DO NOT TRIGGER when: the user says "deploy", "ship", "redeploy" or similar in passing — publishing to production is deliberate and must be named; when the task is tagging a version or cutting a GitHub Release (that is `release`); or when the project publishes from CI only (see §1).
backup
Give a project on the shared VPS a nightly off-box backup, or work on one it already has — provision its Backblaze bucket and bucket-scoped key, write its script and systemd units, render its credentials, and prove the restore by running it rather than describing it. Encodes the toolkit these co-tenants share: restic to B2, one bucket per project, credentials in /etc/<tenant>/backup.env, a staggered timer, and a drill. TRIGGER when: a project needs a backup it does not have; an existing backup needs changing, diagnosing, or restoring from; a nightly backup unit has failed; a restic repository or a Backblaze bucket/key must be created; or someone asks where a project's snapshots live. DO NOT TRIGGER when: the task is a one-off dump taken by hand for a migration or a schema change, a git or source-code backup, or a project that is not a tenant of this box.
heartbeat
Give a scheduled job a dead-man's switch, so its silence is noticed — derive the grace from the job's own cadence, create the check through the healthchecks.io API, put the ping URL where the job's other credentials live, wire the exit codes onto the right endpoints, and prove it by watching the alarm fire. Also audits which scheduled jobs have no check at all. TRIGGER when: a scheduled job (backup, self-check, sync, report) has nothing that would notice it stopping; a heartbeat or dead-man's switch is being added, moved or diagnosed; a healthchecks.io check must be created or its grace chosen; someone asks how a job's failure would be noticed, or which jobs are unmonitored. DO NOT TRIGGER when: the task is provisioning the backup itself (that is `backup`, which hands over here at its last step); alerting for a web service's uptime rather than a scheduled job; or choosing where a secret lives (that is `doppler`).
release
Tag a new version, push to trigger CI, monitor the build, and verify the GitHub release
wrap-up
Close out a section of work. Reviews the current session's transcript for questions you never answered, concerns you passed over, ideas worth memoing, and follow-ups Claude promised but never delivered; settles each one with you, then runs /commit and hands over to /clear. TRIGGER when: the user runs /wrap-up, or says they are ready to finalize, close out, or wrap up the current section of work. DO NOT TRIGGER when: the user only wants to commit (use /commit), to park a single idea (/memo), or to persist durable knowledge (/reflect).
tune-output
Change how Claude's replies are shaped — adopt, revise or reject a response-style rule — then record the pass in a ledger so the next one starts from evidence instead of from scratch. Owns the output style file, the blind A/B harness that tests a candidate before it ships, and the history of what has already been tried. TRIGGER when: the user wants replies formatted or worded differently, brings a response-style idea from another project or repo to evaluate, asks why a style rule exists or is missing, or says an existing style rule is not working. DO NOT TRIGGER when: the subject is prose inside a document or README (that is `docs-style`), commit message wording (`shared/commit-message-rules.md`), a single one-off reply the user just wants rewritten, or a subagent's prompt.
memo
Capture an off-task idea to the project's memo backlog, or list and act on existing memos
github-status
Cross-machine overview of your GitHub-owned local clones — every repo with pending work (uncommitted changes, unpushed commits, inbound remote commits), open issues, or convention versions still to adopt, merged across this machine and its peer, with branch, counts, age of the oldest pending work, how far behind /adopt each clone is, and a one-line summary per working machine. Prints a box table and writes a self-contained HTML report. Each run fetches every repo's origin on both machines 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", "what have I been working on", "which repos are behind on conventions", or "what is uncommitted on the other machine". DO NOT TRIGGER when: user is asking about a single specific repo — that is `/repo-status`, which runs this same scan with `--repo`.
move-project
Move or rename the current project folder without losing the Claude Code data keyed to its old path — session logs, memory and subagent history — by working out the new data directory name and printing the two moves for the user to run from outside the session. TRIGGER when: the user wants to move, rename or relocate the folder of the project they are working in, or asks what happens to their session history and memory if they do. DO NOT TRIGGER when: renaming the GitHub repository without moving the local folder, moving files around inside the project, or creating a new project (that is `github-create`).
adopt
Bring one repo up to date with the conventions defined in the claude dotfiles repo — walk the convention versions this repo has not adopted yet, perform each migration, confirm the continuing rules hold, and hand the new number to /commit. TRIGGER when: the user runs /adopt; a session-start message says this repo is N versions behind or has no convention record; or the user asks where this repo stands on the conventions. DO NOT TRIGGER when: the task is authoring a NEW convention version — that is work in the dotfiles repo, and `claude/conventions/authoring.md` is its contract — or the repo is a third-party clone, which adopts nothing and records nothing.
reflect
Extract and persist conversation learnings before context loss. TRIGGER when: user runs /reflect, or before /clear or compaction.
plannotator-update
Force-update the plannotator plugin by nuking stale caches and reinstalling fresh
docs-relevance
Check that a project's documentation still matches the code and that what should be documented is. TRIGGER when: /commit step 4 runs it, or the user asks whether the docs are stale, out of date, or missing a feature. DO NOT TRIGGER when: the task is how a document is written rather than whether it is true — that is `docs-style`.
docs-style
How a document is written — what it opens with, how it is structured, and which sentences do not belong. TRIGGER when: writing, revising, restructuring or reviewing any long-form prose this repo or a project keeps — a docs/ page, a README section, a learnings file, a convention version README, a memory file body, or a comment running past a few lines. Invoke BEFORE the first draft, not after. DO NOT TRIGGER when: the question is whether a document is still true or complete (that is `docs-relevance`), the text is a commit message (`shared/commit-message-rules.md`), or the subject is how Claude's chat replies are shaped (that is the output style, tuned through `tune-output`).
pull
Bring this branch up to date with its upstream — fetch, judge whether the local edits collide with the incoming commits, move aside only what must move, fast-forward, and resolve what the restore turns up.
repo-status
Cross-machine status of ONE repo — this machine's clone and the peer's, side by side: uncommitted changes, unpushed and inbound commits, branch, age of the oldest pending work, convention versions still to adopt, open issues, and a one-line description of what each machine is mid-way through. Fetches both clones and auto-pulls the clean ones. Prints a short block per machine to the terminal, saying only what is not at its default. TRIGGER when: user asks "/repo-status", wants to know where a single repo stands, "what am I doing in this repo", "is this repo clean on the other machine", "does the desktop have unpushed work here", or "is this repo behind on conventions". DO NOT TRIGGER when: the question is about the fleet rather than one repo (use `/github-status`), or a plain `git status` on this machine answers it — this skill's reason to exist is the OTHER machine's clone and the columns git has no opinion about.
deploy
Configure and run the LOCAL deploy — install the app on this machine or start its dev server — verifying it succeeds
clean-code
Remove dead code, fix duplication, enforce naming conventions, and optimize imports in modified files
document-data-flow
Create or update the data flow architecture document (docs/pages/data-flow.md).
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.
cleanup
Configure an uninstall script and run it to remove the app, its data, and its caches from the system — the "before a clean install" counterpart to deploy
doppler
Store, read, and wire up env-style secrets in Doppler — resolve the real project/config, emit copy-ready command templates, and keep plaintext values out of the transcript. TRIGGER when: a task touches secrets, API keys, tokens, passwords, or `.env` files; before suggesting where a key should live, handing the user a command that carries a secret value, or running any `doppler` command; or the user has a secret on their clipboard. DO NOT TRIGGER when: the secret is a whole document to commit encrypted (use `/transcrypt`), or the project already uses a different secret manager (Vault, a cloud secret manager) — respect it.
github-create
Create a GitHub repository for a local project that already has content but no remote yet. Picks a name, creates the repo (public by default), seeds a LICENSE-only initial commit — MIT, or all rights reserved for a project whose rights stay closed — wires origin, rebases local history onto that commit, and enables email notifications for new issues. Never commits or pushes the project's own files. TRIGGER when: user asks to "create a github repo", "publish this to github", "put this project on github", or runs /github-create in a project with no origin. DO NOT TRIGGER when: the project already has an origin remote (use /commit to push), the user wants to clone or fork an existing repo, or the user wants to cut a release (use /release).
build
Configure build script and run it
reset
Soft-reset unpushed commits back into the working tree for re-committing
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.
hooks
Author, register, and optimize Claude Code hooks — choosing the event and matcher, keeping the per-invocation cost down, and the never-raise contract every hook script owes the harness. TRIGGER when: writing or editing a hook script, adding or changing a `hooks` entry in `settings.json`, diagnosing a hook that never fires or fires too often, or deciding whether something should be a hook at all. DO NOT TRIGGER when: the subject is git hooks (pre-commit, pre-push), React hooks, or Win32 hooks — unrelated senses of the word.
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.
notion
Work with Notion through the right API — the MCP integration by default, and the internal v3 API (token_v2 cookie, /api/v3/) for the operations MCP provably cannot do: select-option recolor/removal, date formats, reminders, conditional row colours, grouped views, bulk row writes, and anything destructive. TRIGGER when: reading or writing Notion pages, databases, rows, schemas or views; an mcp__plugin_Notion_notion__* call failed, was rejected, or silently did nothing; or the user asks to change how a Notion table looks. DO NOT TRIGGER for Notion-adjacent work that never calls an API (writing prose destined for Notion), or when a task-specific skill already owns the database (flightradar24, update-conventions) — start there and come here only for the underlying technique.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.