skills.rest
KGmufassa
KGmufassaCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforce verification steps before marking code changes as complete.

Updated Aug 23, 2026
Search Tags:#workflow#testing#completion#quality-assurance#verify#acceptance-criteria#regressions
One-click install
npx skills add https://github.com/KGmufassa/Escrolly --skill verification-before-completion-kgmufassa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/KGmufassa/Escrolly/tree/main/.opencode/skills/verification-before-completion
Command: npx skills add https://github.com/KGmufassa/Escrolly --skill verification-before-completion-kgmufassa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that work is not marked complete until changes have been verified against the intended behavior, acceptance criteria, and potential regressions.

Core Features & Use Cases

  • Checklist-driven verification after implementing a feature, bug fix, or refactor.
  • Re-run relevant tests and confirm that the original issue is resolved and no regressions are introduced.
  • Enforce a clear completion rule to prevent shipping unverified work.

Quick Start

Run a quick verification pass before closing a task to confirm the change behaves as expected and meets acceptance criteria.

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 code changes before marking a task complete?▼

Checklist-driven verification before completion requires re-running relevant tests and confirming actual behavior matches acceptance criteria. This process validates that bug fixes, features, and refactors are resolved without introducing regressions.

What is checklist-driven verification in software engineering?▼

Checklist-driven verification is a quality-assurance process that enforces test re-runs and regression checks before closing a task. It prevents shipping unverified work by ensuring code changes match intended behaviors and acceptance criteria.

How do I prevent regressions when shipping bug fixes and refactors?▼

Preventing regressions when shipping bug fixes and refactors requires enforcing a clear completion rule that re-runs relevant tests. This verification step confirms that the original issue is resolved and no new behavior mismatches are introduced.

Does verification before completion work for features and refactors?▼

Yes, verification before completion applies to features, bug fixes, and refactors across software projects. It satisfies requirements for test re-runs and regression checks to ensure actual behavior consistently matches expectations and acceptance criteria.

When do I need to enforce a completion rule for code changes?▼

You need to enforce a completion rule for code changes whenever you want to prevent shipping unverified work. This quality-assurance step ensures changes are checked against acceptance criteria and potential regressions before the task is closed.

Related Skills

Explore More Software Engineering Skills→
ZenkakuHiraganaZenkakuHiragana

implementation

Executes repository changes from a normalized task contract with validation.

Community
Advanced
robertzengcnrobertzengcn

ship

Automate base branch merging, tests, version bumps, changelogs, and pull requests.

Community
Advanced
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
malhashemimalhashemi
20

plan-validation

Validate implementation plan phases with automated checks and deviation reports.

Community
Advanced