skills.rest
huyhung9630
huyhung9630COMMUNITY
Explore all skills by this author →
GitHub

omc-verify

Verify software changes with static analysis, unit tests, integration tests, and manual checks.

1|Updated Apr 26, 2026
Search Tags:#quality assurance#software testing#code verification#deployment verification#final review
One-click install
npx skills add https://github.com/huyhung9630/codex_plugin --skill omc-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omc-verify
Source: https://github.com/huyhung9630/codex_plugin/tree/main/plugins/oh-my-codex-workflows/skills/omc-verify
Command: npx skills add https://github.com/huyhung9630/codex_plugin --skill omc-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a final quality gate to ensure that software changes are correct and complete before they are claimed as done.

Core Features & Use Cases

  • Final Quality Gate: Acts as a final check for software changes to verify correctness and completeness.
  • Verification Ladder: Executes a series of checks including static analysis, unit tests, integration tests, manual checks, and reviews of edge cases.
  • Use Case: Use the omc-verify skill to confirm that a new feature works as expected and passes all necessary tests before it is deployed.

Quick Start

Verify the new feature implementation with the omc-verify skill.

Frequently Asked Questions about omc-verify

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

FAQPage Schema
How do I verify software changes before deployment?▼

Yes, deployment verification includes reviewing edge cases alongside static analysis, unit tests, integration tests, and manual checks to ensure software changes handle unexpected scenarios and are fully complete before release.

Can I use a verification ladder to test a new feature implementation?▼

Yes, you can use a verification ladder to test a new feature implementation by running through sequential checks like static analysis and integration tests to confirm the feature works as expected before deployment.

What checks are needed for comprehensive code verification before release?▼

Comprehensive code verification before release requires checks including static analysis, unit tests, integration tests, manual checks, and edge case review to ensure software changes are correct and complete.

Does final quality assurance cover both correctness and completeness of changes?▼

Final quality assurance covers both correctness and completeness of software changes by validating the implementation through a series of tests and manual checks before the changes are claimed as done.

Related Skills

Explore More Software Engineering Skills→
kevindreekevindree

code-review-and-quality

Review code changes for correctness, readability, architecture, security, and performance.

Community
Advanced
Pact-Community-OrganizationPact-Community-Organization
1

quality-gate-enforcement

Automate quality gate verification across pre-code, pre-merge, and pre-deploy stages.

Official
Intermediate
rudometkinrudometkin
1

test

Validate implemented features against specification and Definition of Done.

Community
Intermediate
act70255act70255

testing-qa

Automates unit, integration, E2E, and browser testing with Jest, pytest, and Playwright.

Community
Advanced