Menu
SkillsMP has collected 16 skills from axross/bombdog. Open a skill to review its source and details.
Showing 16 of 16 collected skills.
Drive one unit of work — a GitHub issue, a pull request, or a free-form prompt — from intake to a review-ready pull request in one continuing session; plan and pause for human approval, implement and verify, request the independent review, and address its…
The authoring discipline for agent skills under the host project's skill root (e.g., `.claude/skills/`) — agentskills.io format, frontmatter management and invocation-control fields, kebab-case naming, description and when_to_use writing for discovery,…
The security and privacy review lens for code changes. Covers secrets/env vars, the framework's public/client-exposed env-var prefix (NEXT_PUBLIC_), input validation, access control, public exposure, output-encoding/injection in rendered untrusted content,…
The review methodology for every review task, including post-implementation self-review. Covers reviewer-mode reset, diff scoping with `git status`/`git diff`, severity labels, file-line evidence, fix snippets, verification evidence, second-pass re-review…
The project's baseline working rules. Covers the format/lint loop, scoped change management, current-docs lookup triggers, run-script commands, source-comment and TSDoc doc-comment conventions, verification requirements, data-layer/migration handling,…
Conventions for Playwright end-to-end tests in this project. Covers the `e2e/tests` layout and `<name>.test.ts` naming, `test.step` structuring, stable test-id chained/scoped locators (never text matching), framework-native auto-waiting assertions over manual…
How an agent reads and writes GitHub in this repository's cloud environment — issues, pull requests, comments, labels, reviews, or branches. Covers the sanctioned tool channel (the built-in `mcp__github__*` tools), operating as the connected operator…
Move one unit of in-progress work across session boundaries via a self-contained, downloadable handoff package — a handoff-<unix epoch>.md document plus an optional same-epoch .zip of patches and artifacts. Suspends the outgoing session's state at a safe…
The reviewer's maintainability lens on changed code, on top of the project's development, structure, and any project-defined component/routing rules. Covers naming and file organization, route-local vs shared abstraction boundaries, complexity/readability…
The reviewer's lens on runtime cost and failure-mode behavior. Live lenses for this client-only app: client bundle and dependency weight, asset/image optimization, server/client boundary and render cost, and error-propagation and boundary handling. The…
How to write a product requirement, feature spec, or GitHub issue description. Covers framing the problem/outcome before the solution, separating "what" from "how", explicit non-goals and assumptions, right-sizing scope to the change, testable acceptance…
The bombdog repository's structure and stack conventions. Covers the top-level layout, the Next.js App Router structure under src/app, where unit tests and Playwright e2e tests live, the tooling stack (npm, Biome, Vitest, Playwright), and the agent-harness…
The reviewer's QA lens on verification evidence, on top of development verification and e2e testing rules. Covers format/lint proof, e2e coverage for new routes/features/surfaces, required test-id hooks, intentional snapshot updates, flaky-test investigation,…
The rules for writing, placing, and refactoring any React component or hook function in bombdog. Covers the two-tier design system (domain-agnostic src/components/primitives vs domain src/components/tracker) and the placement decision, the primitives import…
How any bombdog surface should look. Covers which color role to use (accent vs success/danger vs wire hues vs neutrals), borders/shadows/background fills and elevation, which control element fits a decision (segmented toggle, chip toggle-group, dropdown…
Conventions for Vitest unit tests in this project. Covers test framework configuration, explicit test-API imports, colocated test files, describe/case naming and grouping conventions, behavior-focused test design, fixture quality, AHA test abstraction, mocks…