code-acceptance

Name: code-acceptance
Availability: InStock
Author: Yuan

Verify code changes against executable tests and visual evidence.

9|2|Updated Feb 12, 2026

Search Tags:#testing #quality assurance #CI/CD #verification #UI testing #code acceptance

Ready to run

npx skills add https://github.com/leyuan0602-glitch/cc-claude-codex --skill code-acceptance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-acceptance
Source: https://github.com/leyuan0602-glitch/cc-claude-codex/tree/main/code-acceptance
Command: npx skills add https://github.com/leyuan0602-glitch/cc-claude-codex --skill code-acceptance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code changes meet requirements by exclusively relying on automated test outcomes, preventing subjective code reviews from delaying or blocking valid implementations.

Core Features & Use Cases

Test-Based Verification: Executes unit, integration, and E2E tests to confirm functionality against requirements.
Independent Assessment: Focuses solely on whether tests pass or fail, ignoring code implementation details.
UI Aesthetics Check: Validates the visual presentation and user experience of UI changes through screenshots.
Use Case: After a developer implements a new feature, this Skill can be invoked to run all relevant tests and verify the UI looks and behaves as expected before merging the code.

Quick Start

Use the code-acceptance skill to verify the latest code changes by running all associated tests.

Frequently Asked Questions about code-acceptance

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

FAQPage Schema

How do I automate code acceptance verification using automated tests instead of manual review?▼

Automated code acceptance verification runs unit, integration, and E2E tests against code changes to validate functional outcomes and UI aesthetics. Test-based verification confirms requirements are met through executable tests and visual evidence, preventing subjective code reviews from blocking valid implementations.

What is test-based code verification and how does it work for CI/CD pipelines?▼

Test-based code verification executes automated tests to independently assess whether code changes meet acceptance criteria. It focuses solely on test pass or fail outcomes and visual UI evidence, ignoring implementation details. This approach integrates with CI/CD orchestration tools to validate functional requirements.

How to verify UI changes and visual aesthetics before merging code?▼

Verifying UI changes uses screenshot-based visual evidence to validate presentation and user experience. The code-acceptance process checks UI aesthetics through automated visual validation alongside functional tests, ensuring UI changes behave as expected before code is merged.

Can I integrate test-based code verification with orchestration tools like cc-claude-codex?▼

Yes, test-based code verification supports integration with orchestration tools like cc-claude-codex. Running independent test suites through these orchestration tools automates the validation of code changes against acceptance criteria, fitting into existing CI/CD workflows.

Does test-based code acceptance work without reviewing code implementation details?▼

Test-based code acceptance works by focusing exclusively on whether executable tests pass or fail, ignoring code implementation details entirely. It performs independent assessment of functional outcomes and UI aesthetics, ensuring code meets requirements through automated test results rather than subjective review.

What are the limitations of relying solely on automated tests for code acceptance?▼

Relying solely on automated tests for code acceptance means verification is limited to executable test coverage and UI screenshot evidence. Code changes in untested paths or subjective aesthetic nuances not captured by automated assertions may not be fully validated by this approach.