skills.rest
genesis-agents
genesis-agentsCOMMUNITY
Explore all skills by this author →
GitHub

verify-completion

Verify bug fixes and feature implementations with structured completion checklists.

2|3|Updated Nov 9, 2025
Search Tags:#documentation#qa#verification#quality-assurance#bug-fix#regression-testing
One-click install
npx skills add https://github.com/genesis-agents/GenesisPod --skill verify-completion-genesis-agents
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-completion
Source: https://github.com/genesis-agents/GenesisPod/tree/main/.claude/skills/workflow/verify-completion
Command: npx skills add https://github.com/genesis-agents/GenesisPod --skill verify-completion-genesis-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that a bug fix or feature implementation is truly complete before declaring completion, preventing premature closure and rework when the issue reappears.

Core Features & Use Cases

  • Clear completion criteria: defines when work is genuinely done.
  • Structured verification: reproduces the original issue, validates fixes, and checks for regressions.
  • Practical workflows: combines automated checks with manual validation to guard against edge cases.

Quick Start

Execute the verification workflow to confirm the issue is resolved and related regressions are prevented.

Frequently Asked Questions about verify-completion

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

FAQPage Schema
How do I verify a bug fix is truly complete before closing the task?▼

Verify a bug fix is complete by reproducing the original issue, validating the fix, and running regression checks to ensure no new issues are introduced before closure.

What is structured verification for software development workflows?▼

Structured verification combines clear completion criteria, reproducible validation steps, and transparent documentation to confirm bug fixes and feature implementations are genuinely resolved.

How do I check for regressions after implementing a feature or bug fix?▼

Check for regressions by combining automated checks with manual validation to guard against edge cases, ensuring the new feature implementation does not break existing functionality.

Can I use automated checks with manual validation for quality assurance?▼

Yes, practical workflows combine automated checks with manual validation to guard against edge cases and ensure quality assurance by verifying fixes across code, tests, and releases.

Why does premature task closure cause rework in bug tracking?▼

Premature task closure causes rework because the original issue reappears if the bug fix is not fully validated, making structured completion criteria and reproducible verification essential.

When do I need regression testing for feature validation?▼

You need regression testing for feature validation when confirming that new code changes do not negatively impact existing software behavior before declaring the task complete.

Related Skills

Explore More Software Engineering Skills→
Harmitx7Harmitx7
3

plan-writing

Create structured task plans with goals, dependencies, and verification criteria.

Community
Intermediate
lv416elv416e
6

deep-research

Decompose topics into researchable components and synthesize evidence-based conclusions.

Community
Basic
VirtoCommerceVirtoCommerce
2

qa-review-tests

Reviews test suites for structural defects and readiness issues.

Official
Advanced
santosomarsantosomar
1

static-bug-detector

Detect null dereferences, type mismatches, and control flow bugs via static analysis.

Community
Intermediate