AGENT SKILLS · MISSION KIT / bostonaholic

bostonaholic · Agent Skills

43 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.

bostonaholic
Community

rebasing-branches

Rebases the current branch onto its PR or default base, resolves conflicts by intent, re-runs the project's checks, and force-pushes with an explicit lease. Use when the user explicitly asks to rebase the current branch, or when landing-prs calls it on a rebase conflict. Never infer from a behind branch alone. Not for rebasing every open PR; use rebasing-open-prs.

1h installs
1
GitHub stars
2
Updated
Oct 20
bostonaholic
Community

reflecting

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

removing-comments

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

reviewing-design-docs

Reviews a technical design document or RFC adversarially in a fresh-context read-only subagent (coverage, decisions, edge cases, consistency, risks, citations, scope) and returns findings with a verdict. Use when asked to review a design doc, RFC, or technical design. Not for code diffs; use reviewing-code.

1h installs
1
GitHub stars
2
Updated
Oct 20
bostonaholic
Community

reviewing-security

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

scripting-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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

summarizing-friction-logs

Aggregates frog friction logs across every repository in a workspace plus the global log into one prioritized dashboard. Use 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.

1h installs
1
GitHub stars
2
Updated
Oct 20
bostonaholic
Community

testing-the-premise

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

using-gh-cli

Runs GitHub work through the gh CLI and verifies each result. Use when opening a PR, checking CI or failed logs, or handling GitHub issues from a terminal. Merges, closes, reviews, comments, and force operations need an explicit request. Not for landing a PR; use landing-prs.

1h installs
1
GitHub stars
2
Updated
Oct 20
bostonaholic
Community

visualizing-codebases

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

watching-reviewed-prs

Watches a PR the user reviewed in a bounded loop, re-reviewing each author reply or push against the branch, rebutting what the code contradicts, and reporting what it verifies; when the user asks for approval, it also resolves threads and approves once every item settles. Use when the user says "watch this PR for review replies", or when the user asks to watch a PR they reviewed for replies or fixes, or to watch and approve it. Never infer approval from a watch request. Not for the user's own P

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

writing-playbooks

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

writing-technical-design-docs

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.

1h installs
1
GitHub stars
2
Updated
Nov 21
bostonaholic
Community

create-team-skill

Use for creating or revising Team skills. Defines structure, catalog, and validation.

1h installs
1
GitHub stars
11
Updated
Nov 21
bostonaholic
Community

team-implement

Use for executing implementation plans only on explicit request. Never infer from a ready plan.

1h installs
1
GitHub stars
11
Updated
Nov 21
bostonaholic
Community

team-plan

Use for producing tactical implementation plans.

1h installs
1
GitHub stars
11
Updated
Nov 21
bostonaholic
Community

team-research

Use for focused codebase research before changes.

1h installs
1
GitHub stars
11
Updated
Nov 21
bostonaholic
Community

team-structure

Use for breaking reviewed designs into verified implementation slices.

1h installs
1
GitHub stars
11
Updated
Nov 21
bostonaholic
Community

team-worktree

Use for isolated worktrees only on explicit request. Never infer from work needing isolation. Applies project conventions.

1h installs
1
GitHub stars
11
Updated
Nov 21