verify-implementation

Included with Lifetime

$97 forever

Use after implementing changes to run verification commands and ensure tests pass, code builds, and functionality works.

General

What this skill does


# Verify Implementation

Run verification commands after implementing changes to ensure correctness.

## Verification Sources

Check `thoughts/notes/commands.md` (created by `discover-project-commands` skill) for:
- Available test commands
- Linting commands
- Build commands
- Other project-specific verification

## IMPORTANT: Always Use Verification Agent

**DO NOT run verification commands directly in main context.**

Spawn a verification agent to run checks and return summary:

```markdown
Task(subagent_type="Bash",
     prompt="Run verification commands from plan success criteria:
     - make test
     - make lint
     - make build
     [list all automated checks from plan]

     Return concise summary:
     - If all pass: ✅ All verification passed
     - If any fail: ❌ Verification failed
       - List ONLY the failing checks
       - Include first few lines of error
       - Omit stack traces and verbose output

     Maximum output: 2k tokens")
```

**Why use an agent**:
- Raw output can be 10k+ tokens (floods main agent context)
- Agent filters to only essential info (1-2k tokens)
- Keeps main agent focused on implementation
- Part of token management strategy (see `spawn-implementation-agents`)

**Agent returns**:
- ✅ Pass status or ❌ Fail status
- Only failed checks (not successful ones)
- First few lines of errors (not full output)
- Actionable information only

## Common Verification Steps

### 1. Run Tests
Check commands.md, then run appropriate command:
- `make test` - If Make target exists
- `npm test` - If npm script exists
- `go test ./...` - Direct Go command
- `pytest` - Direct Python command

### 2. Run Linting
Check commands.md, then run:
- `make lint` - If Make target exists
- `npm run lint` - If npm script exists
- `golangci-lint run` - Direct Go command
- `eslint .` - Direct JavaScript command

### 3. Build Check
Check commands.md, then run:
- `make build` - If Make target exists
- `npm run build` - If npm script exists
- `go build ./...` - Direct Go command

### 4. Type Checking (if applicable)
- `npm run typecheck` - TypeScript
- `mypy .` - Python
- Go builds include type checking

## Verification Workflow

1. **Check for commands.md**: Read `thoughts/notes/commands.md`
2. **Run automated checks**: Use commands from reference doc
3. **Report results**: Show pass/fail for each check
4. **Manual verification**: Prompt for manual testing if needed

## Handling Failures

If verification fails:
1. Show the error output
2. Analyze the error
3. Fix the issue
4. Re-run verification
5. Don't mark task complete until all checks pass

## Example

```bash
# Read the commands reference
cat thoughts/notes/commands.md

# Run appropriate commands
make test
make lint
make build

# All pass? Mark phase complete in plan
# Any fail? Debug and fix before proceeding
```

## Important

Always spawn agent for verification - never run commands directly in main context.

See `spawn-implementation-agents` skill for full orchestration pattern.

Files: 1

Size: 3.1 KB

Complexity: 6/100

Category: General

Source: https://github.com/eveld/claude/tree/main/skills/verify-implementation

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts