auto-verify

Included with Lifetime

$97 forever

# Auto-Verify Skill (Software Engineering)

General

What this skill does

# Auto-Verify Skill (Software Engineering)

This skill suggests using `/verify` for software engineering tasks that would benefit from systematic verification.

## Design Philosophy

**Be minimal and non-eager.** Users invoke `/verify` when they want it. This skill only suggests verification in specific high-value scenarios where the user might not realize verification would help.

## When to Suggest Verification

Only suggest `/verify` when the user's question involves **ALL** of these:
1. **Significant complexity** - Not a trivial fix or simple question
2. **High risk of subtle bugs** - Async patterns, state management, security
3. **Verifiable claims** - There are specific behaviors that can be tested

### Good Candidates

**Complex code patterns with known pitfalls:**
- React hooks with async behavior (useEffect, useCallback + async)
- Debouncing/throttling implementations
- Race condition scenarios
- Caching strategies
- Authentication/authorization flows

**Security-sensitive operations:**
- Input validation and sanitization
- Token handling and session management
- Password hashing and credential storage
- Encryption/decryption implementations
- Access control and permission checks

**Complex async patterns:**
- Promise chains with error handling
- Concurrent operations with shared state
- Retry logic with backoff strategies
- Streaming and chunked data processing
- WebSocket or real-time connection handling

**Financial and critical operations:**
- Payment processing logic
- Inventory or balance calculations
- Audit logging implementations
- Data migration scripts
- Rate limiting implementations

**Architectural decisions with significant tradeoffs:**
- State management approach (Redux vs alternatives)
- Microservices vs monolith
- Database schema design
- API design patterns

**Bug investigations where the cause is uncertain:**
- "I think the bug is X but not sure"
- Intermittent failures
- Production issues with incomplete information

## When NOT to Suggest

**Do NOT suggest verification for:**
- Simple questions ("How do I center a div?")
- Trivial fixes (typos, simple renames)
- Documentation lookups
- Exploratory coding ("Let's experiment with this approach")
- Clear requirements with obvious implementation
- Time-sensitive requests

## Suggested Response Format

When you do suggest verification, be brief and non-pushy:

```
This [type of task] has some subtle edge cases that `/verify` could catch.
Would you like me to use it, or should I proceed directly?
```

**Examples:**

- "Debouncing has some cleanup gotchas. `/verify` could catch those, or I can proceed directly."
- "Token refresh flows are tricky. Want `/verify` to double-check the implementation?"
- "This architectural decision has significant tradeoffs. `/verify` would evaluate them systematically."

## Important Notes

- **Never auto-invoke** - Only suggest, let user decide
- **Acknowledge if declined** - "Got it, proceeding directly"
- **Don't repeat** - If user declines once, don't suggest again for similar questions
- **Trust the user** - They know when they want thorough verification vs quick answers

Files: 1

Size: 3.1 KB

Complexity: 5/100

Category: General

Source: https://github.com/vertti/se-cove-claude-plugin/tree/main/skills/auto-verify

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