solopowers-receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-31 00:15
Testing & quality
12,974 results
solopowers-systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes (Solopowers/SoloTerm adaptation.)
report-issue
Interactively investigate a bug by grilling the user, exploring the codebase for suspects and solutions, suggesting related test scenarios, and then creating a…
artifact-proof
Use when producing a ZIP, installer, executable, wheel, package, release asset, or other built deliverable.
c-game-regression-testing
Regression-test a single-file C game whose *_test.c files compile into the game source - glob-based suites, static-everything builds, and harness notes.
check-work
Post-change verification workflow. Use after implementation to independently inspect diffs, run the real build and validators, and decide whether the requested…
compatibility-matrix
Use when behavior depends on combinations of operating system, shell, architecture, runtime, model/provider, API revision, application version, or optional…
edge-case-matrix
Use when changing parsers, installers, APIs, inputs, file handling, state machines, or code with many boundary conditions.
failure-injection-testing
Use when software installs, updates, migrates, downloads, writes files, invokes networks, or crosses boundaries where partial failure could corrupt state.
failure-recovery-loop
Use when a test, build, install, CI job, tool call, or repeated attempt fails and the task must continue reliably.
minimal-reproducer
Use when a bug is intermittent, complex, cross-layer, or buried in a large application and the causal input or boundary is not yet isolated.
real-boundary-testing
Use when tests mock subprocesses, filesystems, parsers, databases, networks, CLIs, serialization, or OS/provider integration.
regression-sweep
Use when a bug was fixed or shared behavior, schemas, helpers, installers, or cross-provider integrations changed and sibling regressions may exist.
requirements-traceability
Use when implementing a multi-part request, specification, migration, release, audit, or acceptance-test-driven task.
skyrim-crash-diagnostics
Diagnose Skyrim startup, load, save, or runtime crashes from crash logs, recent changes, plugin lists, DLL inventories, and reproducible evidence without…
skyrim-distr-kid-validation
Cross-framework static and semantic validation for SPID, KID, SkyPatcher, and BOS output.
skyrim-runtime-log-forensics
Interpret Skyrim SKSE, framework, asset, animation, and runtime logs without blaming the wrong field, DLL, mod, or dependency.
skyrim-ship-gate
Mandatory final validation gate for a Skyrim mod release tree or archive. Use after implementation and FOMOD work, before calling a mod finished or ready for…
test-oracle-quality
Use when a test passes but may be checking the wrong signal, mocks its own assumption, snapshots unstable output, or cannot distinguish correct behavior from a…
upgrade-path-testing
Use when a release, installer, schema, configuration, or tool must work for both new users and users upgrading from an older version.
visual-verification
Use when creating, changing, debugging, or claiming completion of anything whose correctness includes how it LOOKS - a website, web or desktop UI, game, HUD,…
whalehunter-strategy
WHALEHUNTERHEDGE v2.0 — a long/short book that positions WITH the smartest money on Hyperliquid and AGAINST the crowd. It segments traders into cohorts by…
integration-e2e-testing
Applies integration and E2E implementation, mock-boundary, and review rules. Use when: writing integration or E2E tests or reviewing their quality.
recipe-quality-profile
Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use…