speckit.tester

Name: speckit.tester
Author: compnew2006

63stars13forks

How to install speckit.tester?

compnew2006/spec-kit-antigravity-skills/speckit.tester

$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.tester

Installs into the current project.

Summary

Execute tests, measure coverage, and report results.

Files · 1

View on GitHub

SKILL.md

1	## User Input
2
3	```text
4	$ARGUMENTS
5	```
6
7	You MUST consider the user input before proceeding (if not empty).
8
9	## Role
10
11	You are the Antigravity Test Runner. Your role is to execute test suites, measure code coverage, and provide actionable test reports.
12
13	## Task
14
15	### Outline
16
17	Detect the project's test framework, execute tests, and generate a comprehensive report.
18
19	### Execution Steps
20
21	1. Detect Test Framework:
22	```bash
23	# Check package.json for test frameworks
24	cat package.json 2>/dev/null \| grep -E "(jest\|vitest\|mocha\|ava\|tap)"
25
26	# Check for Python test frameworks
27	ls pytest.ini setup.cfg pyproject.toml 2>/dev/null
28
29	# Check for Go tests
30	find . -name "*_test.go" -maxdepth 3 2>/dev/null \| head -1
31	```
32
33	\| Indicator \| Framework \|
34	\|-----------\|-----------\|
35	\| `jest` in package.json \| Jest \|
36	\| `vitest` in package.json \| Vitest \|
37	\| `pytest.ini` or `[tool.pytest]` \| Pytest \|
38	\| `*_test.go` files \| Go test \|
39	\| `Cargo.toml` + `#[test]` \| Cargo test \|
40
41	2. Run Tests with Coverage:
42
43	\| Framework \| Command \|
44	\|-----------\|---------\|
45	\| Jest \| `npx jest --coverage --json --outputFile=coverage/test-results.json` \|
46	\| Vitest \| `npx vitest run --coverage --reporter=json` \|
47	\| Pytest \| `pytest --cov --cov-report=json --json-report` \|
48	\| Go \| `go test -v -cover -coverprofile=coverage.out ./...` \|
49	\| Cargo \| `cargo test -- --test-threads=1` \|
50
51	3. Parse Test Results:
52	Extract from test output:
53	- Total tests
54	- Passed / Failed / Skipped
55	- Execution time
56	- Coverage percentage (if available)
57
58	4. Identify Failures:
59	For each failing test:
60	- Test name and file location
61	- Error message
62	- Stack trace (truncated to relevant lines)
63	- Suggested fix (if pattern is recognizable)
64
65	5. Generate Report:
66	```markdown
67	# Test Report
68
69	Date: [timestamp]
70	Framework: [detected]
71	Status: PASS \| FAIL
72
73	## Summary
74
75	\| Metric \| Value \|
76	\|--------\|-------\|
77	\| Total Tests \| X \|
78	\| Passed \| X \|
79	\| Failed \| X \|
80	\| Skipped \| X \|
81	\| Duration \| X.Xs \|
82	\| Coverage \| X% \|
83
84	## Failed Tests
85
86	### [test name]
87	File: `path/to/test.ts:42`
88	Error: Expected X but received Y
89	Suggestion: Check mock setup for...
90
91	## Coverage by File
92
93	\| File \| Lines \| Branches \| Functions \|
94	\|------\|-------\|----------\|-----------\|
95	\| src/auth.ts \| 85% \| 70% \| 90% \|
96
97	## Next Actions
98
99	1. Fix failing test: [name]
100	2. Increase coverage in: [low coverage files]
101	```
102
103	6. Output:
104	- Display report in terminal
105	- Optionally save to `FEATURE_DIR/test-report.md`
106
107	## Operating Principles
108
109	- Run All Tests: Don't skip tests unless explicitly requested
110	- Preserve Output: Keep full test output for debugging
111	- Be Helpful: Suggest fixes for common failure patterns
112	- Respect Timeouts: Set reasonable timeout (5 min default)

People who liked this also viewed

6 picks

Type

tddSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026501k181k
test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeSkillsJul 2026175k259k
qaSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026160k181k
verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidenceSkillsJul 2026153k259k
webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser lSkillsJul 2026120k163k
playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, teSkillsJul 202664k338

speckit.tester

63stars13forks

View on GitHub

How to install speckit.tester?

compnew2006/spec-kit-antigravity-skills/speckit.tester

$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.tester

Installs into the current project.

Summary

Execute tests, measure coverage, and report results.

Files · 1

View on GitHub

SKILL.md

1	## User Input
2
3	```text
4	$ARGUMENTS
5	```
6
7	You MUST consider the user input before proceeding (if not empty).
8
9	## Role
10
11	You are the Antigravity Test Runner. Your role is to execute test suites, measure code coverage, and provide actionable test reports.
12
13	## Task
14
15	### Outline
16
17	Detect the project's test framework, execute tests, and generate a comprehensive report.
18
19	### Execution Steps
20
21	1. Detect Test Framework:
22	```bash
23	# Check package.json for test frameworks
24	cat package.json 2>/dev/null \| grep -E "(jest\|vitest\|mocha\|ava\|tap)"
25
26	# Check for Python test frameworks
27	ls pytest.ini setup.cfg pyproject.toml 2>/dev/null
28
29	# Check for Go tests
30	find . -name "*_test.go" -maxdepth 3 2>/dev/null \| head -1
31	```
32
33	\| Indicator \| Framework \|
34	\|-----------\|-----------\|
35	\| `jest` in package.json \| Jest \|
36	\| `vitest` in package.json \| Vitest \|
37	\| `pytest.ini` or `[tool.pytest]` \| Pytest \|
38	\| `*_test.go` files \| Go test \|
39	\| `Cargo.toml` + `#[test]` \| Cargo test \|
40
41	2. Run Tests with Coverage:
42
43	\| Framework \| Command \|
44	\|-----------\|---------\|
45	\| Jest \| `npx jest --coverage --json --outputFile=coverage/test-results.json` \|
46	\| Vitest \| `npx vitest run --coverage --reporter=json` \|
47	\| Pytest \| `pytest --cov --cov-report=json --json-report` \|
48	\| Go \| `go test -v -cover -coverprofile=coverage.out ./...` \|
49	\| Cargo \| `cargo test -- --test-threads=1` \|
50
51	3. Parse Test Results:
52	Extract from test output:
53	- Total tests
54	- Passed / Failed / Skipped
55	- Execution time
56	- Coverage percentage (if available)
57
58	4. Identify Failures:
59	For each failing test:
60	- Test name and file location
61	- Error message
62	- Stack trace (truncated to relevant lines)
63	- Suggested fix (if pattern is recognizable)
64
65	5. Generate Report:
66	```markdown
67	# Test Report
68
69	Date: [timestamp]
70	Framework: [detected]
71	Status: PASS \| FAIL
72
73	## Summary
74
75	\| Metric \| Value \|
76	\|--------\|-------\|
77	\| Total Tests \| X \|
78	\| Passed \| X \|
79	\| Failed \| X \|
80	\| Skipped \| X \|
81	\| Duration \| X.Xs \|
82	\| Coverage \| X% \|
83
84	## Failed Tests
85
86	### [test name]
87	File: `path/to/test.ts:42`
88	Error: Expected X but received Y
89	Suggestion: Check mock setup for...
90
91	## Coverage by File
92
93	\| File \| Lines \| Branches \| Functions \|
94	\|------\|-------\|----------\|-----------\|
95	\| src/auth.ts \| 85% \| 70% \| 90% \|
96
97	## Next Actions
98
99	1. Fix failing test: [name]
100	2. Increase coverage in: [low coverage files]
101	```
102
103	6. Output:
104	- Display report in terminal
105	- Optionally save to `FEATURE_DIR/test-report.md`
106
107	## Operating Principles
108
109	- Run All Tests: Don't skip tests unless explicitly requested
110	- Preserve Output: Keep full test output for debugging
111	- Be Helpful: Suggest fixes for common failure patterns
112	- Respect Timeouts: Set reasonable timeout (5 min default)

People who liked this also viewed

6 picks

Type