Install
/plugin install bostonaholic --marketplace bostonaholic/skills
Ask your agent:
Install the skills from https://github.com/bostonaholic/skills, refer to the repo's AGENTS.md for instructions.
Or follow the installation instructions.
Skills
Engineering
Addressing PR Comments addressing-pr-comments
Triage and address open PR feedback.
Triages open PR feedback, verifying each review thread, review summary, and comment against the code, then carrying out each item's recommended option, declines and clarifying questions included, and pausing only on exclusions. Use when the user says "address the PR comments", or when the user explicitly asks to address or fix PR comments. Never infer from unresolved comments.
Usage: /addressing-pr-comments [<pr-number-or-url>], or say "address the PR comments"
Calls: attaching-pr-screenshots.
npx skills@latest add bostonaholic/skills --skill addressing-pr-comments
Attaching PR Screenshots attaching-pr-screenshots
Attach local images and short videos to a PR body.
Uploads local images and short videos (mp4, mov, webm) through GitHub's attachment pipeline and writes one verified Screenshots section into a PR body. Use when the user says "attach screenshots to the PR", or when the user explicitly asks to add or attach screenshots to a PR. Never infer from local images. Not for capturing screenshots; use capturing-screenshots.
Usage: /attaching-pr-screenshots [<pr-number-or-url>] [--entries <path> | --copy-from <result.json>], or say "attach screenshots to the PR"
npx skills@latest add bostonaholic/skills --skill attaching-pr-screenshots
Auditing Agent Token Usage auditing-agent-token-usage
Audit Claude Code and Codex token and context costs.
Audits recent Claude Code and Codex session logs for token and context cost: model routing, inherited subagent models, long sessions, compactions, oversized tool results, and unused MCP servers. Use when the user says "audit token usage", or when asked about agent token usage, context costs, session length, model routing, or cost efficiency.
Usage: /auditing-agent-token-usage [<days>], or say "audit token usage"
npx skills@latest add bostonaholic/skills --skill auditing-agent-token-usage
Auditing Complexity auditing-complexity
Rank code complexity hotspots and CRAP change risk.
Ranks where code complexity concentrates in a git repository (cyclomatic complexity, nesting, fan-out, mutable state) and scores CRAP change risk from a coverage file. Read-only. Use when the user says "find complexity hotspots", or when asked for complexity hotspots or change risk. Not for test value; use auditing-tests.
Usage: /auditing-complexity [<path or subsystem> ...] [--out <dir>] [--coverage <file>], or say "find complexity hotspots"
npx skills@latest add bostonaholic/skills --skill auditing-complexity
Auditing Rails Tech Debt auditing-rails-tech-debt
Audit a Rails app for cited tech debt findings.
Audits a Rails app for tech debt, citing each finding to PoEAA, SOLID, or the Rails guides with file:line evidence and before/after code. Use when the user says "audit Rails tech debt", or when auditing Rails for anti-patterns, fat models or controllers, callback abuse, or N+1 queries. Not for over-engineering; use simplifying-ruby-code.
Usage: /auditing-rails-tech-debt, or say "audit Rails tech debt"
Calls: simplifying-ruby-code.
npx skills@latest add bostonaholic/skills --skill auditing-rails-tech-debt
Auditing Repo Security auditing-repo-security
Audit a third-party repo before running it.
Audits a third-party or freshly cloned repo before install or run for install hooks, auto-run files, CVEs, typosquats, and malicious code, graded A-F with a safe-to-run verdict. Use when the user says "is this repo safe to run?", or when asked whether a clone is safe to run, or to audit or scan a third-party repo. Not for security review of a diff or PR; use reviewing-security.
Usage: /auditing-repo-security, or say "is this repo safe to run?"
npx skills@latest add bostonaholic/skills --skill auditing-repo-security
Auditing Tests auditing-tests
Audit a test suite for low-value tests.
Audits a test suite, or a named part, for low-value tests and marks each retain, fix, consolidate, or delete with verified removal evidence. Read-only. Use when the user says "audit the tests", or when asked to audit tests for redundant, junk, or low-value tests. Not for code complexity; use auditing-complexity.
Usage: /auditing-tests [<path or subsystem> ...] [--out <dir>], or say "audit the tests"
npx skills@latest add bostonaholic/skills --skill auditing-tests
Capturing Screenshots capturing-screenshots
Capture verified screenshots of an app.
Captures deterministic, visually verified screenshots of a running web or native app (named screens, states, viewports, dark mode) with a manifest. Use when the user says "take screenshots", or when asked for screenshots of an app or its screens. Not for attaching images to a PR; use attaching-pr-screenshots.
Usage: /capturing-screenshots [--out <dir>] [--url <app-url>] [<what to shoot>], or say "take screenshots"
npx skills@latest add bostonaholic/skills --skill capturing-screenshots
Choosing Determinism choosing-determinism
Move a skill's deterministic steps into scripts it runs.
Moves each step of an agent skill whose correct result is fixed by its inputs into a script the skill runs, leaving the model only judgment. Use when the user says "script the deterministic steps", or when creating a skill, or adding or changing its steps, commands, or parsing. Not for trimming a skill; use cutting-skills.
Usage: /choosing-determinism, or say "script the deterministic steps"
npx skills@latest add bostonaholic/skills --skill choosing-determinism
Configuring Zsh configuring-zsh
Place zsh config in the right startup file.
Chooses the zsh startup file (.zshenv, .zprofile, .zshrc, .zlogin, or a custom plugin under ZSH_CUSTOM) for a configuration change and edits the dotfiles repo source behind the symlink. Use when the user says "update the zsh config", or when adding or moving environment variables, PATH entries, aliases, functions, setopt or zstyle options, or completions in zsh config.
Usage: /configuring-zsh, or say "update the zsh config"
npx skills@latest add bostonaholic/skills --skill configuring-zsh
Code Review Shortcut cr
Start a reviewing-code review with a short name.
Starts a reviewing-code review of an optional diff target, as a short alias for that skill. Use when the user explicitly invokes cr, optionally followed by a branch, PR, commit range, or pasted diff. Never infer from a plain review request; reviewing-code handles that.
Usage: /cr
Explicit invocation only.
Calls: reviewing-code.
npx skills@latest add bostonaholic/skills --skill cr
Diagnosing React Code diagnosing-react-code
Scan a React package and fix its errors.
Runs the react-doctor scanner on a React package, fixes its error diagnostics, and re-runs until none remain. Use when the user says "health-check the React code", or when React components or hooks changed, when finishing a React feature or bug fix, or when asked to health-check React code.
Usage: /diagnosing-react-code, or say "health-check the React code"
npx skills@latest add bostonaholic/skills --skill diagnosing-react-code
Drawing Mermaid Diagrams drawing-mermaid-diagrams
Write, render, and debug Mermaid diagrams.
Writes, edits, and debugs Mermaid diagrams (flowchart, sequence, class, state, ER, Gantt, pie, mindmap, timeline, quadrant, git graph, XY, Sankey, architecture, journey, kanban, block). Use when the user says "draw a diagram", or when the user asks for a diagram, flowchart, ERD, or Mermaid code, or when a Mermaid diagram fails to parse or render.
Usage: /drawing-mermaid-diagrams, or say "draw a diagram"
npx skills@latest add bostonaholic/skills --skill drawing-mermaid-diagrams
Explaining Architecture explaining-architecture
Explain how a subsystem or runtime flow works.
Explains how a subsystem, feature flow, or runtime path works (architecture, data flow, file map, gotchas), with an optional critique by fresh-context critics. Read-only. Use when the user says "how does this work?", or when asked how a subsystem or flow works or where logic belongs. Not for why code is shaped as it is; use investigating-design-rationale. Not for explaining a PR or diff; use explaining-code.
Usage: /explaining-architecture [<subsystem, feature, or question>], or say "how does this work?"
Calls: investigating-design-rationale.
npx skills@latest add bostonaholic/skills --skill explaining-architecture
Explaining Code explaining-code
Explain a PR, diff, or code briefly or in full.
Explains code or code changes in plain language, briefly by default or in full for a reviewer. Use when the user says "explain this PR", or when asked to explain, ELIE, summarize, or break down a PR, diff, branch, file, function, or concept for someone new to the code. Not for how a whole subsystem works; use explaining-architecture.
Usage: /explaining-code [elie] <PR, file, function, branch, or concept>, or say "explain this PR"
Calls: explaining-architecture.
npx skills@latest add bostonaholic/skills --skill explaining-code
Fixing Root Causes fixing-root-causes
Trace each symptom to its root and fix it there.
Traces a bug or failure to its root cause and fixes it there instead of patching the symptom. Use when the user says "find the root cause", or when debugging a crash, failing test, regression, or "fails after restart" bug, or when a fix would add a guard, retry, or workaround to silence an error.
Usage: /fixing-root-causes, or say "find the root cause"
npx skills@latest add bostonaholic/skills --skill fixing-root-causes
Freeing Disk Space freeing-disk-space
Find what fills the disk and clear regenerable files.
Finds what fills a developer machine's disk and frees space by clearing caches, build outputs, and other regenerable files, running each deletion only after approval and never emptying the Trash. Use when the user says "free up disk space", or when a disk is full or nearly full, the user is running out of disk space, builds or containers fail for lack of space, or the user asks for a disk cleanup plan, to free a target amount of space, or to clean up, reclaim space, or delete caches, build outputs, or the Trash to make room.
Usage: /freeing-disk-space, or say "free up disk space"
npx skills@latest add bostonaholic/skills --skill freeing-disk-space
Grooming Backlogs grooming-backlogs
Plan backlog grooming changes for approval.
Grooms a GitHub Projects backlog: verifies issues against the code, ranks and clusters them, and plans milestone, link, and closure changes, or promotes issues to Ready. Proposes tracker changes; each requires approval. Use when the user says "groom the backlog", or when asked to groom, triage, or prioritize a backlog, or to promote issues to Ready.
Usage: /grooming-backlogs [<project-number-or-url>] [--promote <issue-number> | --promote-top [<count>] [--focus <area>]], or say "groom the backlog"
npx skills@latest add bostonaholic/skills --skill grooming-backlogs
Hillclimbing hillclimbing
Iterate on measured changes until the criteria pass.
Iterates toward a goal one measured change at a time, keeping what raises the score and reverting what does not, until a fresh run of the check proves the completion criteria met. Use when the user says "hillclimb", or when the user gives a goal and completion criteria and asks to hillclimb, iterate, or keep going until they pass.
Usage: /hillclimbing, or say "hillclimb"
npx skills@latest add bostonaholic/skills --skill hillclimbing
Improving Codebases improving-codebases
Sweep a codebase with focused improvement lanes.
Sweeps a git repository with focused improvement lanes: implicit state machines made explicit and checked in TLA+, and high-churn files refactored so the next change edits one place. Leaves edits uncommitted. Use when the user says "improve this codebase", or when asked to make implicit state machines explicit or to reduce churn in high-churn files. Never infer from a request to review or explain code. Not for test value or complexity rankings; use auditing-tests or auditing-complexity.
Usage: /improving-codebases [<path or subsystem> ...] [--out <dir>] [--env <NAME> ...], or say "improve this codebase"
npx skills@latest add bostonaholic/skills --skill improving-codebases
Investigating Design Rationale investigating-design-rationale
Investigate why code is shaped as it is.
Answers why code is shaped as it is with an evidence-rated report, tagging each claim [Direct], [Supported], [Inferred], or [Speculative] and closing with a Sources Consulted list that covers git, PRs, tickets, docs, chat, and observability, naming the sources left unchecked. Read-only. Use when the user says "why is it built this way?", or when asked why code is shaped as it is, why a value or limit was chosen, what alternatives were rejected, or what forces shaped a decision, including when the asker offers a guess at the reason. Use it even when commits or PR text are already in context, since a plain answer from them omits the tiers and the unchecked sources. Not for how code works; use explaining-architecture.
Usage: /investigating-design-rationale [<question, file, symbol, or decision>], or say "why is it built this way?"
Calls: explaining-architecture.
npx skills@latest add bostonaholic/skills --skill investigating-design-rationale
Landing PRs landing-prs
Land a reviewed pull request on explicit request.
Lands a reviewed pull request by rebasing onto the base when the branch is behind and resolving any conflicts, running the project's declared pre-merge steps, pushing, waiting for green CI, and squash-merging. Use when the user says "ship it", or when the user explicitly asks to land, ship, or merge a reviewed PR. Never infer from approval, green CI, or completion. Not for a watch that should merge on approval; use watching-authored-prs. Not for updating a PR without landing; use modernizing-prs.
Usage: /landing-prs [<pr-number>], or say "ship it"
Calls: modernizing-prs.
npx skills@latest add bostonaholic/skills --skill landing-prs
Making Code Agent-Friendly making-code-agent-friendly
Audit, review, refactor, and check shared files so many agents can edit code in parallel.
Audits, reviews, and refactors code so many coding agents can change it in parallel without merge conflicts: few shared files, strong boundaries, explicit contracts, fast checks. Also lists the shared files a design or diff edits and flags any file every change appends to. Use when the user says "make this agent-friendly" or "check shared files", or when asked to make code agent-friendly, find where parallel agents will collide, or name the shared files a feature edits or the files every change appends to. Not for general code review; use reviewing-code.
Usage: /making-code-agent-friendly [audit [<path>...] | review [<diff target>] | refactor <finding> | shared-files [<design or feature> | <diff target>] [<package directory>]], or say "make this agent-friendly"
npx skills@latest add bostonaholic/skills --skill making-code-agent-friendly
Merging Dependabot PRs merging-dependabot-prs
Plan and merge safe Dependabot updates one at a time, or only request rebases.
Analyzes open Dependabot PRs for semver level, CI, breaking changes, and security fixes, then squash-merges approved patch and minor updates one at a time, or only comments @dependabot rebase; supports a dry run. Use when the user explicitly asks to merge, process, or rebase Dependabot PRs. Never infer from green CI, an approved Dependabot PR, or stale or conflicting Dependabot PRs.
Usage: /merging-dependabot-prs [PR numbers] [--rebase-only] [--dry-run]
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill merging-dependabot-prs
Modernizing PRs modernizing-prs
Bring a PR up to date, or recommend reworking or closing it.
Brings the checked-out PR up to date after checking its intent against base changes. MODERNIZE rebases, re-runs checks, and force-pushes with a lease; REWORK or CLOSE stops. Use when the user says "modernize this PR", or when the user explicitly asks to bring a PR up to date or rebase it, or when landing-prs or watching-authored-prs calls it on a conflict. Never infer from a behind branch alone.
Usage: /modernizing-prs [<pr-number-or-url>], or say "modernize this PR"
npx skills@latest add bostonaholic/skills --skill modernizing-prs
Opening PRs opening-prs
Open a draft PR or refresh its body after a push.
Opens a draft pull request for the current branch, or refreshes the body of its open PR after a push, from the branch diff and an optional inputs file. Use when the user says "open a PR", or when the user explicitly asks to open or refresh a pull request for the current branch. Never infer from finished work or passing checks. Not for a gh stack layer; use stacking-prs. Not for screenshots; use attaching-pr-screenshots.
Usage: /opening-prs [<pr-number-or-url>] [--inputs <path>], or say "open a PR"
npx skills@latest add bostonaholic/skills --skill opening-prs
Prototyping UI prototyping-ui
Build 3 to 5 interactive UI prototypes and recommend one.
Builds 3 to 5 interactive HTML, CSS, and JavaScript prototypes of one feature, each a different interaction model, then compares their usability as an experienced UX designer and recommends one. Use when the user says "prototype this", or asks to prototype, mock up, or compare design options for a screen, flow, or component. Not for building the production feature.
Usage: /prototyping-ui, or say "prototype this"
npx skills@latest add bostonaholic/skills --skill prototyping-ui
Proving Claims proving-claims
Prove claims or a PR test plan with rated evidence.
Proves or disproves claims, or the test plan of a PR, by trying to falsify each and rating the strongest evidence reached (PROVEN, PARTIAL, DISPROVEN, UNPROVEN). Changes nothing. Use when the user says "prove it", or when asked to prove, verify, or fact-check claims or a PR test plan with evidence. Not for writing acceptance criteria; use writing-acceptance-criteria.
Usage: /proving-claims [<claims> | <pr-number-or-url>], or say "prove it"
npx skills@latest add bostonaholic/skills --skill proving-claims
Redesigning From First Principles redesigning-from-first-principles
Redesign as if a new requirement was always there.
Redesigns an existing design as if a new requirement had been a founding assumption, then propagates it to every reference and delivers it in working increments. Use when the user explicitly asks to redesign for a requirement or from first principles. Never infer from a feature request. Not for redoing an attempt; use redoing-implementations.
Usage: /redesigning-from-first-principles
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill redesigning-from-first-principles
Redoing Implementations redoing-implementations
Rebuild the current work as a simpler design.
Rebuilds the current implementation from scratch as the simplest design that satisfies what was learned, after the user approves the design. Use when the user explicitly asks to redo the work, start over, scrap the approach, or rewrite it more simply. Never infer from a failing or complex implementation. Not for fitting a new requirement into an existing design; use redesigning-from-first-principles.
Usage: /redoing-implementations
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill redoing-implementations
Removing Comments removing-comments
Remove every source comment outside a short keep list, fixing root causes with approval.
Removes every source comment outside a short keep list, flagged by a fresh-context reviewer, and, with approval, fixes root causes and encodes enforceable constraints in types, tests, or lint. Use when the user explicitly asks to remove or clean up code comments. Never infer from a diff containing comments.
Usage: /removing-comments [<files-or-diff>]
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill removing-comments
Reviewing Code reviewing-code
Review a diff in a fresh subagent and post the review.
Reviews a code diff (PR, branch, commit range, working tree, or a diff already in the conversation) in a fresh-context read-only subagent, because a session holding the conversation is a biased reviewer, posts its Conventional Comments findings inline and its APPROVE, REQUEST CHANGES, or COMMENT verdict to the pull request when one exists, and returns a short summary. Use when the user says "code review", or when asked to review code, a diff, or a PR, including a pasted diff, a .diff or .patch file, or a diff shown earlier; never review it inline. Not for design docs; use reviewing-design-docs. Not for a security-focused review; use reviewing-security.
Usage: /reviewing-code [<diff target>], or say "code review"
npx skills@latest add bostonaholic/skills --skill reviewing-code
Reviewing Design Docs reviewing-design-docs
Adversarially review a technical design document.
Reviews a technical design document or RFC adversarially in fresh-context read-only subagents, one per lens, and returns one merged report with a verdict. Use when the user says "review this design doc", or when asked to review a design doc, RFC, or technical design. Not for code diffs; use reviewing-code.
Usage: /reviewing-design-docs [<design-doc-path-or-url>], or say "review this design doc"
npx skills@latest add bostonaholic/skills --skill reviewing-design-docs
Reviewing Security reviewing-security
Security-review a diff in a fresh-context read-only subagent.
Reviews a code diff for exploitable security vulnerabilities in a fresh-context read-only subagent, reporting only high-confidence findings with an exploit scenario and fix. Use when the user says "security review", or when asked for a security review of code, a diff, a branch, or a PR. Not for general review; use reviewing-code. Not for a third-party clone; use auditing-repo-security.
Usage: /reviewing-security [<diff target>], or say "security review"
npx skills@latest add bostonaholic/skills --skill reviewing-security
Scripting the Work scripting-the-work
Build a rerunnable tool that does or proves the work.
Builds a codemod, script, generator, query, or check that does or proves non-trivial work, so a reviewer reruns it instead of trusting hand edits. Use when the user explicitly asks to script the work, write a codemod, or make a change rerunnable. Never infer from a small edit. Not for a skill's own steps; use choosing-determinism.
Usage: /scripting-the-work
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill scripting-the-work
Simplifying Ruby Code simplifying-ruby-code
Find or fix over-engineered Ruby and Rails code.
Rewrites over-engineered Ruby and Rails classes (stateless service objects, behaviorless value objects, class-method-only classes, deep inheritance, needless metaprogramming) as Data, Struct, Hash, modules, or pure functions, after finding every caller and getting a green test baseline, or reports findings when asked to review. Use when the user says "simplify this Ruby", or when asked to refactor, simplify, review, or cut boilerplate from a Ruby or Rails class, value object, service object, gem, or branch diff (hand-written initialize, readers, ==, eql?, or hash; call-only classes; Struct vs Data), or when tests need heavy mocking. Not for a broad Rails tech-debt audit; use auditing-rails-tech-debt.
Usage: /simplifying-ruby-code, or say "simplify this Ruby"
npx skills@latest add bostonaholic/skills --skill simplifying-ruby-code
Stacking PRs stacking-prs
Split a large change into stacked PRs with gh stack.
Splits a large change into stacked pull requests with GitHub's gh stack CLI. Use when the user says "stack PRs" or "create a PR stack", or when a change is too big to review as one PR, has dependent parts, or overlaps the same author's open PRs, or when creating, updating, syncing, merging, or recovering a gh stack stack.
Usage: /stacking-prs, or say "stack PRs"
npx skills@latest add bostonaholic/skills --skill stacking-prs
Summarizing Friction Logs summarizing-friction-logs
Prioritize frog friction logs across a workspace.
Aggregates frog friction logs across every repository in a workspace plus the global log into one prioritized dashboard. Use when the user says "show the friction dashboard", or when asked for the friction dashboard, all known friction or papercuts across repos, to list friction logs, or to decide which friction to fix first.
Usage: /summarizing-friction-logs, or say "show the friction dashboard"
npx skills@latest add bostonaholic/skills --skill summarizing-friction-logs
Testing Behavior, Not Implementation testing-behavior-not-implementation
Assert observable behavior, not internals, in tests.
Checks each test asserts what the code's users can observe, so it fails when that behavior breaks and passes when only internals change. Use when the user says "test behavior, not implementation", or when writing, changing, or keeping a test. Not for auditing a whole suite; use auditing-tests.
Usage: /testing-behavior-not-implementation, or say "test behavior, not implementation"
npx skills@latest add bostonaholic/skills --skill testing-behavior-not-implementation
Testing the Premise testing-the-premise
Test the premise repeated failed fixes share.
Writes down the premise that repeated failed fixes share and tests it before any further fix that assumes it. Use when the user says "test the premise", or when a second fix to the same failure has not worked, such as a limit, timeout, pool size, or retry count raised again while the error persists. Never infer from one failed fix. Not for a first diagnosis; use fixing-root-causes.
Usage: /testing-the-premise, or say "test the premise"
npx skills@latest add bostonaholic/skills --skill testing-the-premise
Untangling Codebases untangling-codebases
Refactor a codebase so each change lands in one place.
Refactors a whole codebase in one pass so each change lands in one place: catalogs hidden links, needless links, surplus code, and special cases, redesigns to remove their shared causes, and repeats until nothing worth fixing is left. Use when the user says "untangle this codebase", or when asked to refactor a whole codebase so changes land in one place. Never infer from a bug fix or feature request. Not for one new requirement; use redesigning-from-first-principles.
Usage: /untangling-codebases [<area or concern to focus on>], or say "untangle this codebase"
npx skills@latest add bostonaholic/skills --skill untangling-codebases
Updating Bostonaholic Skills updating-bostonaholic-skills
Update the bostonaholic plugin installs and skill copies to the latest release.
Updates the bostonaholic skills plugin installs (Claude Code, Codex, the Cursor plugin clone) and the skill copies in the Antigravity, OpenCode, Cursor, and Grok Bot skill directories to the latest release tag. Use when the user explicitly asks to update the bostonaholic skills. Never infer from an outdated skill or a version mismatch. Not for installing; use INSTALL.md.
Usage: /updating-bostonaholic-skills
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill updating-bostonaholic-skills
Updating Changelogs updating-changelogs
Add Unreleased bullets to an existing CHANGELOG.md.
Adds user-facing bullets under the Unreleased section of an existing Keep a Changelog CHANGELOG.md for the commits since the last release, skipping changes the section already covers. Use when the user says "update the changelog", or when the user explicitly asks to add changelog entries. Never infer from a finished change. Not for summarizing shipped work; use summarizing-shipped-work.
Usage: /updating-changelogs [<repo>], or say "update the changelog"
npx skills@latest add bostonaholic/skills --skill updating-changelogs
Verifying Production Changes verifying-production-changes
Confirm a merged change took effect in production.
Verifies a merged change took effect in production by revision ancestry and cohort sampling, and reports a bound over sampled requests rather than "fully deployed". Use when the user says "is it live in prod?", or when asked to confirm or report whether a merged change is live or deployed in production, before answering, even when the build-info, status, or deploy output is already in hand; also when gating on a deploy reaching the fleet, sequencing deploys, or verifying a one-time migration, backfill, or cleanup. Not for CI or build state.
Usage: /verifying-production-changes, or say "is it live in prod?"
npx skills@latest add bostonaholic/skills --skill verifying-production-changes
Visualizing Codebases visualizing-codebases
Build an interactive site that visualizes a codebase.
Builds an interactive static D3 site that visualizes a codebase, starting with a C4 view of system context, containers, components, and code, with dependency cycles between modules and classes. Use when the user says "visualize this codebase", or asks for C4 diagrams or a map of a codebase's structure and dependency cycles. Not for prose walkthroughs; use explaining-architecture.
Usage: /visualizing-codebases, or say "visualize this codebase"
npx skills@latest add bostonaholic/skills --skill visualizing-codebases
Watching Reviewed PRs watching-reviewed-prs
Watch a PR you reviewed and approve once feedback settles.
Watches a PR the user reviewed in a bounded loop, re-reviews each settlement of their feedback against the branch, resolves or rebuts, and approves once every item settles. Use when the user explicitly asks to watch and approve a PR they reviewed. Not for the user's own PR; use watching-authored-prs.
Usage: /watching-reviewed-prs [<pr-number-or-url>]
Explicit invocation only.
npx skills@latest add bostonaholic/skills --skill watching-reviewed-prs
Writing Commit Messages writing-commit-messages
Write a 50/72 Conventional Commits message.
Writes a git commit message for staged changes with a 50/72 subject and body, a Conventional Commits type, footers, and issue citations, keeping any subject, type, or body line the caller fixes byte for byte. Use when the user says "write a commit message", or when the user explicitly asks for a commit message. Never infer from staged changes or a request to commit.
Usage: /writing-commit-messages, or say "write a commit message"
npx skills@latest add bostonaholic/skills --skill writing-commit-messages
Writing No Comments writing-no-comments
Write code with no comments outside a short keep list.
Bans source comments outside a short keep list in code the agent writes or edits. Use when the user says "no comments", or when about to write or edit code, tests, scripts, or config: load it before the first code edit of every task, including code a subagent writes. Not for cleaning existing comments. The user runs removing-comments.
Usage: /writing-no-comments, or say "no comments"
npx skills@latest add bostonaholic/skills --skill writing-no-comments
Writing No Tests writing-no-tests
Write no tests. I dare you.
Dares the agent to write no tests. Use when the user says "write tests", or when the user asks to write, skip, or fix tests. Always infer from a request to write, skip, or fix tests.
Usage: /writing-no-tests, or say "write tests"
npx skills@latest add bostonaholic/skills --skill writing-no-tests
Writing Playbooks writing-playbooks
Turn a resolved incident session into a runnable playbook.
Writes a playbook an on-call agent can run from the session that resolved an alert or incident. Use when the user says "write the playbook", "turn this into a playbook", or "make a runbook for this". Not for session learnings; use reflecting.
Usage: /writing-playbooks, or say "write the playbook"
npx skills@latest add bostonaholic/skills --skill writing-playbooks
Writing Technical Design Docs writing-technical-design-docs
Draft a directionally correct technical design doc.
Drafts technical design docs that are directionally correct, not perfect, deciding one-way doors, deferring two-way doors, and naming unknowns. Use when the user says "write a design doc", or when asked to write, draft, or author a design doc, RFC, tech spec, or architecture proposal. Not for reviewing a design; use reviewing-design-docs.
Usage: /writing-technical-design-docs, or say "write a design doc"
Calls: reviewing-design-docs.
npx skills@latest add bostonaholic/skills --skill writing-technical-design-docs
Productivity
Being Extremely Brief being-extremely-fucking-brief
Keep every response extremely brief.
Keeps every reply to the user to three lines or fewer, with no preamble, restated question, recap, or closing offer. Use when the user says "be brief", or when about to reply to the user: load it before every reply in every session, including plain questions, recommendations, and comparisons, even when no other skill applies.
Usage: /being-extremely-fucking-brief, or say "be brief"
npx skills@latest add bostonaholic/skills --skill being-extremely-fucking-brief
Composing Agent Prompts composing-agent-prompts
Compose a source-cited task prompt for another agent.
Composes a self-contained, source-cited task prompt for another coding agent to execute in a target repository, without running the task. Use when the user says "write a prompt for another agent", or when the user asks to write, draft, or hand off a prompt, brief, or task spec for another agent. Not for system prompts; use writing-system-prompts.
Usage: /composing-agent-prompts [<task description>] [--repo <path>] [--out <path>], or say "write a prompt for another agent"
Calls: improving-prompts.
npx skills@latest add bostonaholic/skills --skill composing-agent-prompts
Conducting Deep Research conducting-deep-research
Research an evidence review plus a funding map.
Conducts source-backed, goal-directed research that combines a scholarly evidence review with an institution, company, or funding map. Use when the user says "deep research", or when a request needs both an evidence review and an organization or funding map. Not for quick lookups or general research write-ups.
Usage: /conducting-deep-research, or say "deep research"
npx skills@latest add bostonaholic/skills --skill conducting-deep-research
Cutting Skills cutting-skills
Audit or trim an agent skill to its behavioral core.
Audits or trims an existing agent skill to its behavioral core and narrows over-broad trigger metadata. Use when the user says "cut this skill", or when the user asks to cut, simplify, shorten, de-slop, or reduce the context cost or trigger aggressiveness of a SKILL.md or skill folder. Never infer from a skill being long or edited for another purpose.
Usage: /cutting-skills, or say "cut this skill"
Calls: hillclimbing.
npx skills@latest add bostonaholic/skills --skill cutting-skills
Defining Problems defining-problems
Interview the user until the problem is defined.
Interviews the user in rounds of numbered questions until the problem is defined, with who has it, evidence, impact, and success criteria, before any solution. Use when the user says "what problem are we solving?", or asks to define, frame, or clarify a problem. Never infer from a plain feature or bug request. Not for drafting a design; use writing-technical-design-docs.
Usage: /defining-problems, or say "what problem are we solving?"
Calls: writing-acceptance-criteria.
npx skills@latest add bostonaholic/skills --skill defining-problems
Improving Prompts improving-prompts
Compress and clarify an existing prompt.
Compresses and clarifies an existing LLM prompt through concept elevation, verifying that no original instruction is lost. Use when the user says "improve this prompt", or when the user supplies a prompt or prompt file and asks to improve, tighten, optimize, or refine it. Not for writing a new prompt; use writing-system-prompts.
Usage: /improving-prompts <prompt text or file path containing the prompt to improve>, or say "improve this prompt"
npx skills@latest add bostonaholic/skills --skill improving-prompts
Learning From Mistakes learning-from-mistakes
Turn a correction into an approved rule and the check that enforces it.
Codifies the latest correction or mistake in the conversation as a short imperative rule in the project or global CLAUDE.md or AGENTS.md and, for a project lesson, proposes the highest check that makes the mistake impossible, after the user approves. Use when the user says "learn from this mistake", or when the user asks to learn from a mistake, remember a lesson for next time, add a rule to CLAUDE.md, make a mistake impossible, or not repeat a behavior. Not for a whole session; use reflecting.
Usage: /learning-from-mistakes, or say "learn from this mistake"
npx skills@latest add bostonaholic/skills --skill learning-from-mistakes
Reflecting reflecting
Mine a session or named sources for durable learnings.
Mines a session transcript, past agent sessions, or named sources such as PR review comments for durable learnings, then proposes approval-gated edits to skills, AGENTS.md, or docs and tracker issues. Use when the user says "reflect" or "reflect on ...", or explicitly asks to reflect on a session or sources. Never infer from session end or friction.
Usage: /reflecting [what to reflect on], or say "reflect"
npx skills@latest add bostonaholic/skills --skill reflecting
Summarizing Shipped Work summarizing-shipped-work
Summarize merged PRs into a shipped-work report.
Summarizes the user's merged GitHub PRs for a timeframe into a grouped, linked shipped-work report with highlights, and offers to update a brag document. Use when the user says "what shipped?", or when asked what the user shipped (this week, last month, a quarter, since a date), for a status update, or to update a brag doc.
Usage: /summarizing-shipped-work [timeframe] [owner...], or say "what shipped?"
npx skills@latest add bostonaholic/skills --skill summarizing-shipped-work
Writing Acceptance Criteria writing-acceptance-criteria
Write acceptance criteria that a check can prove.
Writes or rewrites acceptance criteria until each is provable: one observable outcome with a named check that can fail. Use when the user says "write acceptance criteria", or asks to write, rewrite, or tighten acceptance criteria or a definition of done. Not for proving work meets them; use proving-claims.
Usage: /writing-acceptance-criteria, or say "write acceptance criteria"
npx skills@latest add bostonaholic/skills --skill writing-acceptance-criteria
Writing Prose writing-prose
Write plain, short prose for people.
Writes and edits prose for people in a plain, conversational, short house style with no em dashes. Use when the user says "write this up", or when drafting or revising documentation, READMEs, explanations, blog posts, or other human-facing prose. Not for prompts written for agents; use writing-system-prompts or composing-agent-prompts.
Usage: /writing-prose, or say "write this up"
npx skills@latest add bostonaholic/skills --skill writing-prose
Writing System Prompts writing-system-prompts
Write or review a system prompt.
Writes and reviews system prompts for AI tools, agents, chatbots, and LLM products using a fixed section order and a quality checklist. Use when the user says "write a system prompt", or when drafting a system prompt or auditing one for missing stop criteria, tool rules, constraints, or examples. Not for compressing an existing prompt; use improving-prompts.
Usage: /writing-system-prompts, or say "write a system prompt"
npx skills@latest add bostonaholic/skills --skill writing-system-prompts