skills.rest
romiluz13
romiluz13COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require fresh verification outputs before claiming completion in cc10x-router workflows.

161|25|Updated Oct 22, 2025
Search Tags:#code quality#testing#quality assurance#developer workflow#verification#risk management#task completion
One-click install
npx skills add https://github.com/romiluz13/cc10x --skill verification-before-completion-romiluz13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/verification-before-completion
Command: npx skills add https://github.com/romiluz13/cc10x --skill verification-before-completion-romiluz13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a critical verification step before any task is marked complete, preventing incomplete work, missed requirements, and unverified fixes. It provides a structured checklist to ensure all criteria are met, tests pass, and functionality is fully validated, guaranteeing high-quality, production-ready outcomes.

Core Features & Use Cases

  • Mandatory Verification Checklist: Provides a comprehensive checklist to ensure all aspects of a task are verified (e.g., tests passing, linting, type checks, manual testing).
  • Functionality Validation: Ensures that the implemented functionality works as expected across all user, admin, and system flows.
  • Evidence-Based Confirmation: Requires command outputs, logs, and test results as evidence of successful verification.
  • Risk & Open Question Identification: Prompts for documentation of any residual risks or open questions before completion.
  • Use Case: Before marking a bug fix as complete, use this skill to run all relevant tests, verify the bug is no longer reproducible, check for any new issues, and document the verification steps and outcomes.

Quick Start

Verify the recent implementation of the user profile update feature, ensuring all tests pass and the functionality works as expected.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my code changes before marking a task complete?▼

Verification before completion requires running fresh tests, linting, and build commands to collect evidence of success. Execute the full verification command, read the output, confirm it matches your requirements, then document the results before declaring the task done.

What should I check when verifying a bug fix or feature implementation?▼

Verification covers tests passing, linting checks succeeding, type checks clearing, and functionality working across all user and admin flows. Run all relevant commands, capture outputs as evidence, reproduce the original issue to confirm it's resolved, and check for new problems introduced.

Why is evidence-based verification important in development workflows?▼

Evidence-based verification prevents incomplete work, missed requirements, and unverified fixes from reaching production. Requiring command outputs, logs, and test results as proof ensures high-quality outcomes and catches problems before completion.

Can I use this verification approach with different testing frameworks and build tools?▼

Yes, verification applies across any testing framework, linter, or build tool by identifying the proving command for your stack, running it fully, reading the output, and validating results against your completion criteria.

What risks should I document when completing a task?▼

Document any residual risks, open questions, known limitations, or edge cases discovered during verification. This record helps track potential issues and informs decisions about follow-up work or monitoring after completion.

Related Skills

Explore More Software Engineering Skills→
DethonDethon
3

verification-before-completion

Run full verification commands and report fresh outputs before claiming completion.

Community
Basic
k2worksk2works

tracking-progress

Analyze project progress from git logs, test results, and architectural data.

Community
Advanced
adamayoungadamayoung
1

test

Execute unit test suites and capture diagnostic output via Xcode or make.

Community
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic