GitHub
testing-anti-patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
☆ 38View skill
Testing & security AI Skills
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Categories: Testing & security
Testing & security Clear filters
Browse skills
GitHub
defense-in-depth-validation
Validate at every layer data passes through to make bugs impossible
☆ 38View skill
GitHub
condition-based-waiting
Replace arbitrary timeouts with condition polling for reliable async tests
☆ 38View skill
GitHub
test-driven-development-tdd
Write the test first, watch it fail, write minimal code to pass
☆ 38View skill
GitHub
code-review-reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
☆ 38View skill
GitHub
validating-inputs
Check all external inputs for validity - garbage in, nothing out, never garbage out
☆ 38View skill
GitHub
gardening-skills-wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
☆ 38View skill
GitHub
writing-evergreen-comments
Write comments explaining WHAT and WHY, never temporal context or history
☆ 38View skill
GitHub
clarification-expert
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
☆ 37View skill
GitHub
commit
Create micro-commits (minimal incision) with at least one validation signal per commit.
☆ 37View skill
GitHub
gen-plan
Generate iterative `plan-N.md` files in the repo root (max N=5). Use only when asked; clarify before `plan-1.md`; stop at `plan-5.md`.
☆ 37View skill
GitHub
select
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
☆ 37View skill
GitHub
beads
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
☆ 37View skill
GitHub
trace
TRACE (Type/Readability/Atomic/Cognitive/Essential) lens for explaining code and proposing improvements (no edits applied).
☆ 37View skill
GitHub
tk
Software surgery: contract → invariants → creative search → inevitable incision; minimal diff, compositional core, proof signal.
☆ 37View skill
GitHub
fix
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity); requires a validation signal.
☆ 37View skill
GitHub
imp
Unified shipping + TRACE self-review protocol (beads, proof, PR). Explicit-only.
☆ 37View skill
GitHub
gen-beads
Convert a project plan written in a Markdown file into a complete bd beads graph (tasks, subtasks, dependencies) using only bd for creation and edits, then review and optimize each bead. Use when asked to beadi...
☆ 37View skill
GitHub
universalist
Algebra-Driven Design (ADD): model domains via minimal algebra + laws; encode in types; test laws.
☆ 37View skill
GitHub
prove-it
Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries.
☆ 37View skill
GitHub
ship
Finalize work after validation: confirm a signal, capture proof in PR description and bead comment (if beads), and open a PR (no merge). Use when asked to ship, finish, or open a PR.
☆ 37View skill
GitHub
web-browser
Automate Chrome/Chromium via CDP: navigate, click, fill forms, evaluate JS, screenshot, scrape.
☆ 37View skill
GitHub
zig
Zig runbook: performance (SIMD + threads), build/test, comptime patterns, allocators, build.zig/build.zig.zon, zero-copy parsing, C interop.
☆ 37View skill
GitHub
join
PR autopilot: create/manage PRs, enforce CI gates, apply surgical fixes, and squash-merge via `gh`.
☆ 37View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.