skills.rest
LiGoldragon
LiGoldragonCOMMUNITY
Explore all skills by this author →
Website𝕏@LiGoldragonGitHub

verification-before-completion

Run linters, tests, and build commands before marking code changes complete.

1|Updated Feb 18, 2026
Search Tags:#code review#verification#commit quality#pre-commit checks#development hygiene
One-click install
npx skills add https://github.com/LiGoldragon/Mentci-AI --skill verification-before-completion-ligoldragon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/LiGoldragon/Mentci-AI/tree/main/.pi/skills/verification-before-completion
Command: npx skills add https://github.com/LiGoldragon/Mentci-AI --skill verification-before-completion-ligoldragon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fosters transparency in code commits and PRs by mandating thorough verification of code quality and correctness before claiming work is complete.

Core Features & Use Cases

  • Pre-Commit Verification: Runs checks like linters, tests, and build commands before a developer claims that work is ready for review.
  • Code of Conduct Enforcement: Ensures adherence to code purity rules and integrity of contributions.
  • Use Case: When developers intend to merge or submit PRs, they use this Skill to execute predefined checks, ensuring all tests pass, code is clean, and changes adhere to repository standards.

Quick Start

Before claiming work complete, run 'nix shell .#verify-commit -- my_commit_hash' and verify that no issues are reported.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I run pre-commit checks to verify code quality before creating a PR?▼

Run pre-commit verification by executing 'nix shell .#verify-commit -- my_commit_hash' to validate code quality, enforce linters, and ensure all changes pass tests before claiming work is complete.

What is pre-merge code inspection and when do I need it?▼

Pre-merge code inspection is the process of validating completeness and quality of changes before submission. You need it when working in repositories where maintainable, robust code and compliance with coding standards are required.

Does this pre-commit verification work with my development environment?▼

This pre-commit verification applies to development environments requiring maintainable, robust code. It targets repositories needing thorough pre-merge inspections and enforces compliance with defined coding standards.

What's the best way to enforce coding standards and development hygiene before submission?▼

Enforce development hygiene by using this Skill to mandate thorough verification of correctness and quality before completion, ensuring transparency in commits and adherence to code purity rules.

Why should I verify code changes before claiming work is complete?▼

Verifying code changes before claiming completion prevents bugs and errors in commits. It fosters transparency, ensures tests pass, and guarantees changes adhere to repository standards before submission.

Related Skills

Explore More Software Engineering Skills→
ArvorCoArvorCo
96

constitution

Create or update a project constitution defining coding principles and governance rules.

Community
Advanced
DinudaDinuda

pr-report

Generate HTML or Markdown review reports for pull requests and branches.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced