alexbruno/dev-skills

verification-and-testing

Enforce evidence-based verification and meaningful test coverage before claiming any task is complete.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/alexbruno/dev-skills --skill verification-and-testing

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Verification & Testing

Never claim a change works, passes, or is complete without fresh, direct verification evidence collected after the final edit.

Core Rule

Evidence before completion claims. If you did not run a check after your last change and observe its output, do not report it as passing.

1. Align Verification with workflow/SPEC.md

  • Map every acceptance criterion in workflow/SPEC.md and the verification strategy in workflow/PLAN.md to a concrete check (automated test, build, lint, typecheck, or explicit runtime check).
  • Treat untested acceptance criteria as incomplete work.

2. Write Meaningful Tests

  • Test behavior, not implementation details: Assert observable outputs, state transitions, and side effects so tests survive safe refactoring (code-simplification).
  • Cover the edges: Include boundary values, empty/null inputs, invalid states, and error paths—not just the happy path.
  • Keep tests isolated and deterministic: Avoid shared mutable state, real network calls, or time-dependent flakiness unless explicitly testing integration boundaries.
  • Never weaken assertions: Do not relax, skip, or mock away the core behavior under test just to make a suite green.

3. Execution Gate After Final Edit

Before handing off work or moving to workflow/REVIEW.md:

  1. Run the relevant unit/integration tests, linter, typechecker, and build commands.
  2. Confirm all executed checks pass with zero skipped or relaxed assertions.
  3. Report the exact scope of what was run (e.g., full suite vs. targeted subset, any environment limitations).
同じリポジトリから

関連する Skills

すべての Skills
alexbruno
コミュニティ

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日
alexbruno
コミュニティ

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior. Use this skill after implementing a feature, during refactoring, or when addressing code review feedback—especially when code feels over-engineered, deeply nested, or takes unnecessary detours to do simple things.

1時間の導入数
1
GitHub Stars
0
更新日
11月13日