Code Acceptance
Independent code acceptance skill. Use when verifying completed work before committing, merging, or claiming done. Performs test-based verification only: unit tests, E2E tests, and integration tests. Only cares whether outcomes match expectations, not code implementation. Works standalone or as cc-claude-codex Phase 3.
Install
npx skills add leyuan0602-glitch/cc-claude-codex --skill code-acceptancegit clone --depth 1 https://github.com/leyuan0602-glitch/cc-claude-codex.git /tmp/cc-claude-codex
mkdir -p ~/.claude/skills
cp -r /tmp/cc-claude-codex/code-acceptance ~/.claude/skills/code-acceptancePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Acceptance: Test-Based Verification You are an independent code acceptance verifier. Your job is to verify that code changes produce the expected outcomes through automated tests. **You do NOT review code implementation** — only test results determine PASS or FAIL. ## Core Principles 1. **Zero trust** — Never trust the executor's claims (Codex, developer, or any agent). All judgments come from running actual tests. 2. **Tests are the only evidence** — PASS/FAIL is determined solely by whether tests pass. No code review, no style opinions, no implementation critique. 3. **Outcome over implementation** — You don't care HOW the code works, only THAT it works as specified by the requirements. ## Input Collection ### Mode A: cc-claude-codex Integration When called from cc-claude-codex Phase 3: - **Requirements**: Read `.cc-claude-codex/status.md` → extract `### Requirement:` blocks and `#### Scenario:` (Given/When/Then) - **Changes**: `git diff HEAD~1 --stat` (for changed files overview only) - **Reference data**: Codex's returned progress and final output — marked `[REF]`, used for cross-checking only, never as evidence ### Mode B: Standalone When invoked directly: - **Requirements**: From conversation context, or ask the user - **Changes**: `git diff HEAD~1 --stat` (default), or user-specified diff range - If no clear requirements provided: run existing test suite only ### Step 0: Build Context 1. Run `git diff HEAD~1 --stat` → list changed files
Details
- Skill name
code-acceptance- Repository
- leyuan0602-glitch/cc-claude-codex
- Path
code-acceptance/SKILL.md- License
- MIT
- Repo updated
- 2 March 2026
FAQ
What does the Code Acceptance skill do?
Independent code acceptance skill. Use when verifying completed work before committing, merging, or claiming done. Performs test-based verification only: unit tests, E2E tests, and integration tests. Only cares whether outcomes match expectations, not code implementation. Works standalone or as cc-claude-codex Phase 3.
How do I install the Code Acceptance skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add leyuan0602-glitch/cc-claude-codex --skill code-acceptance. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Acceptance popular?
It lives in leyuan0602-glitch/cc-claude-codex, which has 9 GitHub stars and 2 forks.
Related skills
Cc Claude Codex
9leyuan0602-glitch/cc-claude-codex
Development skill where Claude Code acts as supervisor and Codex acts as executor. Auto-trigger for implementation, debugging, refactoring, testing, and other dev tasks.
Multi Agent Verify
9leyuan0602-glitch/cc-claude-codex
Multi-agent parallel verification. Spawns 3 independent agents (OpenCode CLI, Codex CLI, Claude Task subagent) in separate git worktrees to review, test, and fix code. Synthesizes results and applies final fixes on the original branch.
Design SDK
9canonical/use-workshop-skill
Design, build, and publish Workshop SDKs with sdkcraft — interview and research the software, generate sdkcraft.yaml with hooks and spread smoke tests, iterate via sdkcraft try plus workshop refresh, write the README, then onboard the SDK repo with version branches, CI workflows, and renovate. Use when creating or maintaining a publisher-side (Store) SDK from its own repository — "design an SDK for X", "create an sdkcraft.yaml", "set up renovate and CI for my SDK repo".
Dmk Intent Vocabulary
9LedgerHQ/agent-skills
Map developer intent and natural language to the correct Ledger Device Management Kit (DMK) components, operations, and API methods. Use when a developer's request is phrased informally, incompletely, or in terms of outcomes rather than API methods, when the intent is ambiguous and needs mapping to a specific DMK component or operation, or when a developer asks 'how do I...', 'what's the difference between...', or describes a symptom rather than an API.
Zemax Python Connect
9Hao-xl/zemax-python-connect
当用户提到 Zemax OpticStudio Python 连接、ZOS-API 配置、独立应用程序、交互扩展、CreateNewApplication、ConnectAsExtension、ZOSAPI_NetHelper.dll、NotAuthorized、PrimarySystem None、Instance Number,或在连接 Python 与 Zemax 时遇到 --replace-current 时使用。
Ledger Dmk Implementation
9LedgerHQ/agent-skills
Execute Ledger Device Management Kit (DMK) signing operations safely: initialize the SDK, establish a device session, verify device state, open the correct chain app, perform signing or device management operations, and return the result. Use when a developer needs to implement a signing operation (transaction, message, typed data), derive or retrieve an address from a Ledger device, send any command to a Ledger device, or perform device management operations such as genuine check, app install, or app uninstall.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.