testing-debugging-verification

Étoiles1

Forks0

Mis à jour20 juin 2026 à 09:37

Use when writing tests, practicing TDD, debugging failures, flaky tests, Go Delve sessions, Go mocks, Rust tests, Go tests, or verifying changes before claiming success.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

bnema

bnema/pi-public

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

15 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

project-backlog

bnema/pi-public

Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.

2026-06-201

agent-workflows

bnema/pi-public

Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.

2026-06-201

write-a-skill

bnema/pi-public

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

2026-06-201

architecture-security

bnema/pi-public

Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.

2026-06-201

hexcheck

bnema/pi-public

Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.

2026-06-201

improve-codebase-architecture

bnema/pi-public

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

2026-06-201

name	testing-debugging-verification
description	Use when writing tests, practicing TDD, debugging failures, flaky tests, Go Delve sessions, Go mocks, Rust tests, Go tests, or verifying changes before claiming success.

Testing Debugging Verification Router

Load only the matching sub-skill:

Trigger	Read
TDD, red-green-refactor, test-first implementation, integration-test-first work	`testing-debugging-verification/subskills/tdd/SKILL.md`
diagnose this, debug this, hard bug, performance regression, reproduce/minimise/instrument/fix loop	`testing-debugging-verification/subskills/diagnose/SKILL.md`
Go tests, table tests, subtests, benchmarks, fuzzing, coverage	`testing-debugging-verification/subskills/golang-testing/SKILL.md`
Rust tests, async tests, property tests, mocking, coverage	`testing-debugging-verification/subskills/rust-testing/SKILL.md`
Delve, dlv, breakpoints, goroutines, core dump, Go debugging	`testing-debugging-verification/subskills/go-delve-debugging/SKILL.md`
mockery, Go interface mocks, testify EXPECT, RunAndReturn	`testing-debugging-verification/subskills/go-mockery/SKILL.md`
verification loop, final proof, comprehensive session verification	`testing-debugging-verification/subskills/verification-loop/SKILL.md`