Loading...
Loading...
Found 961 Skills
Use when validating implementation against spec artifacts before archive — not for design, planning, or implementation
Verifies that implemented code is actually integrated into the system and executes at runtime, preventing "done but not integrated" failures. Use when marking features complete, before moving ADRs to completed status, after implementing new modules/nodes/services, or when claiming "feature works". Triggers on "verify implementation", "is this integrated", "check if code is wired", "prove it runs", or before declaring work complete. Works with Python modules, LangGraph nodes, CLI commands, API endpoints, and service classes. Enforces Creation-Connection-Verification (CCV) principle.
EmailListVerify integration. Manage Users. Use when the user wants to interact with EmailListVerify data.
Background knowledge for droid-control workflows -- not invoked directly. Deliverable verification against commitments.
Verify code for security issues including hardcoded secrets, input validation, error exposure, and dependency vulnerabilities. Use when asked to "verify security", "check for secrets", or "scan for vulnerabilities".
Automate Postgrid Verify tasks via Rube MCP (Composio). Always search tools first for current schemas.
Use before claiming work is done, fixed, or passing — requires running verification commands and confirming output before any success claim. Prevents false completion claims, unverified assertions, and "should work" statements.
Verify a spec-driven change is complete and correctly implemented. Checks task completion, implementation evidence, and spec alignment.
Verify changes follow nearest-scoped AGENTS.md rules: group changed files by nested scope, auto-fix formatting, run lint/tests, and report violations. Use when the user wants scoped compliance checks for changed files.
Verify structure analysis output against source code. Check file:line references, component completeness, and Mermaid diagram validity. Runs as independent Critic in fork context. Use when: verify structure, check structure map, validate phase 1, re-verify-structure.
Use when the user wants to validate that implemented code matches its specifications, generate integration tests from feature files, or check if code still satisfies existing scenarios. Trigger after implementation completes a feature. Also use when the user asks "does the code do what we specified?" or "generate tests from the feature files".
**Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.