skills.rest
quangphu1912
quangphu1912COMMUNITY
Explore all skills by this author →
Website𝕏@quangphu1912GitHub

verification-before-completion

Run verification commands and review outputs before committing changes.

1|1|Updated Apr 7, 2026
Search Tags:#verification#code integrity#development practices#commit check#work integrity
One-click install
npx skills add https://github.com/quangphu1912/codebase-analyzer --skill verification-before-completion-quangphu1912
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/quangphu1912/codebase-analyzer/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/quangphu1912/codebase-analyzer --skill verification-before-completion-quangphu1912

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and teams maintain honesty and integrity in their work by enforcing verification before making claims of completion or correctness.

Core Features & Use Cases

  • Verification Workflow: Ensures that verification commands are run and output is reviewed before making any claims of success.
  • Evidence-Based Claims: Promotes a culture of evidence before assertions, reducing the risk of shipping incomplete or incorrect work.
  • Use Case: Before submitting a pull request, use this Skill to verify that all tests pass, linters are clean, and the build succeeds, ensuring that the code is ready for review.

Quick Start

Before pushing code, run 'codebase-analyzer:verify-all' to ensure all checks are passed.

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 integrity before committing changes?▼

Evidence-based claims require running all defined verification commands and reviewing their outputs before committing. This enforces work integrity by ensuring assertions of correctness are backed by actual test and build results.

What is the best way to ensure evidence-based completion before a pull request?▼

The best way to ensure evidence-based completion before a pull request is to run a verification workflow. This process executes all specified checks, such as tests and linters, and requires reviewing the output to confirm the code is ready for review.

How do I run verification checks to prevent shipping incomplete work?▼

You can prevent shipping incomplete work by executing verification commands like 'codebase-analyzer:verify-all' before pushing code. This mechanism runs all defined checks and requires you to review the output to ensure the project state is correct.

Do I need specific verification commands to check my project state before committing?▼

Yes, you need a list of defined verification commands to check your project state before committing. The verification process requires these commands to run and a mechanism to review their outputs for ensuring development integrity.

Why does verifying output before claiming completion improve development workflows?▼

Verifying output before claiming completion improves development workflows by promoting a culture of evidence before assertions. It reduces the risk of shipping incorrect work by ensuring all checks are run and reviewed, maintaining honesty in project states.

Related Skills

Explore More Software Engineering Skills→
j7-devj7-dev
19

verification-loop

Automate multi-phase code verification with build, type, lint, test, and security scans.

Community
Advanced
GenproMMGenproMM

gsd-ship

Automate pull request creation, review triggering, and merge tracking in Git repositories.

Official
Intermediate
d-o-hubd-o-hub
11

rust-code-quality

Review Rust code quality across eight dimensions including async patterns and error handling.

Community
Advanced
rstacruzrstacruz
13

verify-implementation

Automate post-change verification with preflight checks, targeted tests, and manual validation.

Community
Intermediate