verification-loop

Name: verification-loop
Author: affaan-m

232kstars35kforks

How to install verification-loop?

affaan-m/ecc/verification-loop

$npx -y skills add affaan-m/ECC --skill verification-loop

Installs into the current project.

Summary

A comprehensive verification system for Claude Code sessions.

Files · 1

View on GitHub

SKILL.md

1	# Verification Loop Skill
2
3	A comprehensive verification system for Claude Code sessions.
4
5	## When to Use
6
7	Invoke this skill:
8	- After completing a feature or significant code change
9	- Before creating a PR
10	- When you want to ensure quality gates pass
11	- After refactoring
12
13	## Verification Phases
14
15	### Phase 1: Build Verification
16	```bash
17	# Check if project builds
18	npm run build 2>&1 \| tail -20
19	# OR
20	pnpm build 2>&1 \| tail -20
21	```
22
23	If build fails, STOP and fix before continuing.
24
25	### Phase 2: Type Check
26	```bash
27	# TypeScript projects
28	npx tsc --noEmit 2>&1 \| head -30
29
30	# Python projects
31	pyright . 2>&1 \| head -30
32	```
33
34	Report all type errors. Fix critical ones before continuing.
35
36	### Phase 3: Lint Check
37	```bash
38	# JavaScript/TypeScript
39	npm run lint 2>&1 \| head -30
40
41	# Python
42	ruff check . 2>&1 \| head -30
43	```
44
45	### Phase 4: Test Suite
46	```bash
47	# Run tests with coverage
48	npm run test -- --coverage 2>&1 \| tail -50
49
50	# Check coverage threshold
51	# Target: 80% minimum
52	```
53
54	Report:
55	- Total tests: X
56	- Passed: X
57	- Failed: X
58	- Coverage: X%
59
60	### Phase 5: Security Scan
61	```bash
62	# Check for secrets
63	grep -rn "sk-" --include=".ts" --include=".js" . 2>/dev/null \| head -10
64	grep -rn "api_key" --include=".ts" --include=".js" . 2>/dev/null \| head -10
65
66	# Check for console.log
67	grep -rn "console.log" --include=".ts" --include=".tsx" src/ 2>/dev/null \| head -10
68	```
69
70	### Phase 6: Diff Review
71	```bash
72	# Show what changed
73	git diff --stat
74	git diff HEAD~1 --name-only
75	```
76
77	Review each changed file for:
78	- Unintended changes
79	- Missing error handling
80	- Potential edge cases
81
82	## Output Format
83
84	After running all phases, produce a verification report:
85
86	```
87	VERIFICATION REPORT
88	==================
89
90	Build: [PASS/FAIL]
91	Types: [PASS/FAIL] (X errors)
92	Lint: [PASS/FAIL] (X warnings)
93	Tests: [PASS/FAIL] (X/Y passed, Z% coverage)
94	Security: [PASS/FAIL] (X issues)
95	Diff: [X files changed]
96
97	Overall: [READY/NOT READY] for PR
98
99	Issues to Fix:
100	1. ...
101	2. ...
102	```
103
104	## Continuous Mode
105
106	For long sessions, run verification every 15 minutes or after major changes:
107
108	```markdown
109	Set a mental checkpoint:
110	- After completing each function
111	- After finishing a component
112	- Before moving to next task
113
114	Run: /verify
115	```
116
117	## Integration with Hooks
118
119	This skill complements PostToolUse hooks but provides deeper verification.
120	Hooks catch issues immediately; this skill provides comprehensive review.

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

verification-loop

232kstars35kforks

View on GitHub

How to install verification-loop?

affaan-m/ecc/verification-loop

$npx -y skills add affaan-m/ECC --skill verification-loop

Installs into the current project.

Summary

A comprehensive verification system for Claude Code sessions.

Files · 1

View on GitHub

SKILL.md

1	# Verification Loop Skill
2
3	A comprehensive verification system for Claude Code sessions.
4
5	## When to Use
6
7	Invoke this skill:
8	- After completing a feature or significant code change
9	- Before creating a PR
10	- When you want to ensure quality gates pass
11	- After refactoring
12
13	## Verification Phases
14
15	### Phase 1: Build Verification
16	```bash
17	# Check if project builds
18	npm run build 2>&1 \| tail -20
19	# OR
20	pnpm build 2>&1 \| tail -20
21	```
22
23	If build fails, STOP and fix before continuing.
24
25	### Phase 2: Type Check
26	```bash
27	# TypeScript projects
28	npx tsc --noEmit 2>&1 \| head -30
29
30	# Python projects
31	pyright . 2>&1 \| head -30
32	```
33
34	Report all type errors. Fix critical ones before continuing.
35
36	### Phase 3: Lint Check
37	```bash
38	# JavaScript/TypeScript
39	npm run lint 2>&1 \| head -30
40
41	# Python
42	ruff check . 2>&1 \| head -30
43	```
44
45	### Phase 4: Test Suite
46	```bash
47	# Run tests with coverage
48	npm run test -- --coverage 2>&1 \| tail -50
49
50	# Check coverage threshold
51	# Target: 80% minimum
52	```
53
54	Report:
55	- Total tests: X
56	- Passed: X
57	- Failed: X
58	- Coverage: X%
59
60	### Phase 5: Security Scan
61	```bash
62	# Check for secrets
63	grep -rn "sk-" --include=".ts" --include=".js" . 2>/dev/null \| head -10
64	grep -rn "api_key" --include=".ts" --include=".js" . 2>/dev/null \| head -10
65
66	# Check for console.log
67	grep -rn "console.log" --include=".ts" --include=".tsx" src/ 2>/dev/null \| head -10
68	```
69
70	### Phase 6: Diff Review
71	```bash
72	# Show what changed
73	git diff --stat
74	git diff HEAD~1 --name-only
75	```
76
77	Review each changed file for:
78	- Unintended changes
79	- Missing error handling
80	- Potential edge cases
81
82	## Output Format
83
84	After running all phases, produce a verification report:
85
86	```
87	VERIFICATION REPORT
88	==================
89
90	Build: [PASS/FAIL]
91	Types: [PASS/FAIL] (X errors)
92	Lint: [PASS/FAIL] (X warnings)
93	Tests: [PASS/FAIL] (X/Y passed, Z% coverage)
94	Security: [PASS/FAIL] (X issues)
95	Diff: [X files changed]
96
97	Overall: [READY/NOT READY] for PR
98
99	Issues to Fix:
100	1. ...
101	2. ...
102	```
103
104	## Continuous Mode
105
106	For long sessions, run verification every 15 minutes or after major changes:
107
108	```markdown
109	Set a mental checkpoint:
110	- After completing each function
111	- After finishing a component
112	- Before moving to next task
113
114	Run: /verify
115	```
116
117	## Integration with Hooks
118
119	This skill complements PostToolUse hooks but provides deeper verification.
120	Hooks catch issues immediately; this skill provides comprehensive review.

People who liked this also viewed

6 picks

Type