bostonaholic
Review Skills published by bostonaholic, their source repositories, maintenance signals, and identity status.
- Skills
- 4
- Repository stars
- 11
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Creator
- Canonical name
- bostonaholic
- Public sources
- 1
- License context
- MIT
Source entries
Agent Skills from bostonaholic
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
bostonaholic/team
create-team-skill
Authoring guide for creating a new skill in this plugin, matching the conventions the existing skills already use. Establishes the three decisions every skill must make before any prose is written: how it is invoked (entry point vs building block), how it acquires its input, and how it manages the context window. Do NOT hand-write a SKILL.md directly. Trigger on "create a skill", "add a new skill", "scaffold a skill", "write a SKILL.md", or a description of new skill functionality the user wants
bostonaholic/team
pr-watch-as-reviewer
Watch a pull request you are reviewing until your feedback is settled, re-review each settlement, then approve once: poll GitHub in ~31-minute cycles for up to 24 hours until every review thread you opened is resolved and every plain PR comment you posted has a later push behind it, re-review each settlement against the current branch (the change or the reply must actually meet the comment's concern), then cast one attributed, SHA-cited approval and stop. A settlement that fails re-review stops
bostonaholic/team
team-implement
Execute the implementation phase. Includes test-first sub-step (writing failing tests, mechanical confirmation gate) and adversarial verification (5 parallel reviewers with hard-gate retry loop). Trigger on "implement this", "execute the plan", or "/team-implement".
bostonaholic/team
test-style
Test style rules and the flaky-test red-flag catalog — behavior-not-implementation, DAMP setup, narrow assertions, deterministic-input rules (clock, randomness, ordering, hermetic boundaries), the fidelity ladder, and the audit checklist. Load when writing tests, auditing test quality, or reviewing changed test files for flaky patterns.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository