What is test-implementation?

A command for implementing and reporting comprehensive tests for the latest project phase. Tests are automated checks that verify software behavior.

Use it to identify missing test cases, add coverage for implemented features, verify dependencies and helpers, and report the testing results.

It connects the implementation plan to the needed unit, widget, integration, and golden tests, while checking the test environment and existing coverage.

How Consiliency/Flutter-Structurizr configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Consiliency/Flutter-Structurizr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Consiliency/Flutter-Structurizr/main/.claude/commands/test-implementation.md

Clone the repo

git clone --depth 1 https://github.com/Consiliency/Flutter-Structurizr

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/test-implementation/github.svg)](https://agentmods.dev/commands/consiliency/flutter-structurizr/test-implementation)

Your own site

<a href="https://agentmods.dev/commands/consiliency/flutter-structurizr/test-implementation"><img src="https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/test-implementation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/consiliency/flutter-structurizr/test-implementation"><img src="https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/test-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 846 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00846
Opus 5.5	$0.00000	$0.00338
Sonnet 5.5	$0.00000	$0.00169
Haiku 4.5	$0.00000	$0.00085

Measured 2mo ago against content hash 6ef58bcf2d06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-implementation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/test-implementation.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Command: Test Latest Implementation

Test Plan Analysis

Analyze the testing plan for the current phase:
- Review testing sections in the implemented phase document (specs/phase{N}_implementation_plan.md)
- Check specs/testing_plan_template.md for additional testing guidance
- Identify test categories required (unit, widget, integration, golden)
- Note any specific testing frameworks or dependencies needed
- Check for recent test-related best practices and lessons learned in CLAUDE.md and specs/testing_plan.md
Verify testing environment:
- Check existing test files related to the implemented phase
- Identify test dependencies needed in pubspec.yaml
- Install any missing testing dependencies
- Verify testing utilities and helpers are available

Test Implementation

For each implemented feature: Think Hard
- Check if existing tests already cover the functionality
- Create new tests for any untested functionality
- Consider potential name conflicts with Flutter built-ins
- Reference the ai_doc/ directory for specific framework and library documentation
- Use Web Fetch, Web Search, and Fetch tools to find examples and documentation if not in /ai_docs
  - Compile new documentation that you find into a library specific markdown file and save it in /ai_docs for future reference
- Ensure test coverage for:
  - Normal use cases
  - Edge cases
  - Error handling
  - Integration with existing components
Follow testing best practices: Ultra Think
- Create unit tests for domain models and application logic
- Implement widget tests for UI components
- Add integration tests for end-to-end functionality
- Create golden tests for visual regression testing when appropriate
- Use mocks and fakes for isolating components
- Handle name conflicts in test files properly (hide directives, alias types)
- Add comments explaining complex test scenarios
Run all tests:
- Use the provided testing scripts in the scripts/ directory:
  - scripts/run_all_tests.sh to run all tests
  - scripts/run_domain_tests.sh for domain model tests
  - scripts/run_layout_tests.sh for layout tests
  - scripts/run_documentation_tests.sh for documentation tests
  - scripts/run_ui_tests.sh for UI component tests
- Run tests for the specific components implemented
- Run any affected existing tests
- Run flutter test --coverage and report coverage metrics
- Document test results and failures
- Debug and fix any test failures
- Rerun tests until all pass
- If new test strategies or helpers are developed, update the testing plan in specs/
- Document any persistent test failures or workarounds for future developers

Read the full file on GitHub · 95 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 95 lines · 0 tokens per session scan A 6ef58bcf2d06

Subscribe to this mod's changes

test-implementation is a command published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 846 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

test-implementation next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
test-implementationConsiliency/Flutter-Structurizr	Command	7	11d ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Flutter-Structurizr: Command for Claude Code