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日