verification-stack

Included with Lifetime

$97 forever

Python verification pipeline: ruff + pytest + type checking in sequence. Use INSTEAD OF superpowers:verification-before-completion when the project uses Python tooling. MUST run before any commit, merge, or PR claim in a Python project. Trigger: "run all checks", "verify the code", "is the build green", "run ruff and pytest", or proactively before claiming work is done.

General

What this skill does


# Verification Stack

## Goal

Run automated quality gates (format, lint, type check, test) as deterministic verification instead of manual approval. Verification replaces permission prompts — if checks pass, proceed; if they fail, fix and retry.

**Core Principle — Asymmetry of Verification**: Many tasks are easier to verify than to solve. Software development is highly verifiable through tests, linters, type checkers, and build systems.

## Dependencies

### Tools

- **Bash** — Runs all verification commands

### Connectors (language-specific)

| Language | Format | Lint | Types | Test |
|---|---|---|---|---|
| Python | `ruff format` | `ruff check` | `mypy` | `pytest` |
| TypeScript | `pnpm format` | `pnpm lint` | `tsc` | `vitest` |
| Go | `go fmt` | `golangci-lint` | `go build` | `go test` |

## Context

### Pipeline Order (Fast-Fail)

Run checks in this order — stop at first failure:

1. **Format** (auto-fix) — `uv run ruff format .`
2. **Lint** (auto-fix where possible) — `uv run ruff check . --fix`
3. **Type check** — `uv run mypy src/`
4. **Tests** (fast subset) — `uv run pytest tests/ -x --tb=short`
5. **Full test suite** — `uv run pytest tests/ --cov=src/`
6. **Security** (optional) — `uv run bandit -r src/ --severity-level high`

### Common Failure Patterns

| Failure | Fix |
|---|---|
| Lint: unused import | Remove the import |
| Type: missing return | Add return type annotation |
| Test: assertion failed | Fix logic or update test |
| Format: style violation | Auto-fix handles this |

## Process

### Step 0: Load Stored Feedback

```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/feedback_manager.py autonomous-sdlc show-feedback
```

Apply relevant feedback: **verification**, **general**.

### Step 1: Run the Pipeline

For Python projects:

```bash
uv run ruff format . && uv run ruff check . --fix && uv run mypy src/ && uv run pytest tests/ -x --tb=short
```

### Step 2: Handle Failures

1. **Read the error output** — Don't guess, analyze the actual failure
2. **Fix the specific issue** — Make targeted changes
3. **Re-run verification** — Confirm the fix works
4. **Continue** — Move to next task only when green

### Step 3: Continuous Verification

In autonomous workflows:
- **Before starting** — Check baseline is green
- **After each change** — Run relevant subset
- **Before closing a Bead** — Run full suite
- **Before merge** — Run full suite + integration tests

```bash
# Quick check during development
uv run pytest tests/test_specific.py -x

# Full verification before closing Bead
uv run ruff format . && uv run ruff check . --fix && uv run mypy src/ && uv run pytest tests/
```

## Output

A green or red verification result. Green means proceed. Red means fix and retry. No human approval needed — the pipeline is the gate.

### One-Command Script

For projects that want a single entry point:

```bash
#!/bin/bash
# scripts/verify.sh
set -e
echo "=== Formatting ===" && uv run ruff format .
echo "=== Linting ===" && uv run ruff check . --fix
echo "=== Type Checking ===" && uv run mypy src/
echo "=== Tests ===" && uv run pytest tests/ -x --tb=short
echo "=== All checks passed ==="
```

Files: 2

Size: 6.5 KB

Complexity: 19/100

Category: General

Source: https://github.com/joshuaoliphant/claude-plugins/tree/main/plugins/autonomous-sdlc/skills/verification-stack

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