Skip to content

搵技能.../

Agent Skill Search Engine

搜尋

搜尋
分類
職業

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Verifying Before Completion | Skills Pool

技能檔案

Verifying Before Completion

Final verification before marking work complete. Use when: finishing a task, completing a plan, or before reporting success. Keywords: verify, check, complete, done, finish

sitien1730 星標2026年4月12日

職業
分類: 代碼質素

技能內容

Overview

Never declare work complete without verification. Run tests, check the original requirements, and confirm no regressions.

Verification Checklist

1. Run Integration Checks

Execute the exact integration checks from the phase or final plan
All tests must pass
No new errors or warnings

2. Check Original Requirements

Review the original user request
Verify each acceptance criterion is met
Confirm file changes match expected scope

3. Run CP4 Phase Review

Apply CP4 to determine:

PASS - Spec fully satisfied
PASS_WITH_DEBT - Usable with explicit non-blocking debt
FAIL - Does not satisfy original request

4. Check for Regressions

相關技能

快速安裝

Verifying Before Completion

npx skillvault add sitien173/sitien173-superpowers-ccg-skills-verifying-before-completion-skill-md

下載 Skill 打開源碼倉庫

作者: sitien173
星標: 0
更新時間: 2026年4月12日
職業

本頁內容

Run related test suites
Verify no unintended side effects
Check that existing functionality still works

Completion Report

After verification, report:

Task completed
Files changed
Integration check result
CP4 status
Any open follow-ups

Rule

Do not report final completion until all phases return PASS or PASS_WITH_DEBT and final integration checks pass. If CP4 returns FAIL, address gaps before completion.

02

Verification Checklist

031. Run Integration Checks

042. Check Original Requirements

053. Run CP4 Phase Review

064. Check for Regressions

07Completion Report

軟件質量保證分析師同測試人員

Openclaw Release Maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

自動化工具

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft184.0k

Add Policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

microsoft184.0k

軟件質量保證分析師同測試人員