azoth-test

Generates unit tests for specified code via a Codex-based workflow command contract.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-test
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-test
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a Codex-visible entrypoint to trigger Azoth's /test workflow, enabling automated unit test generation for specified code.

Core Features & Use Cases

  • Codex-native entrypoint: exposes a dedicated surface to invoke the /test workflow.
  • Execution contract awareness: reads commands/test/command.yaml as the source of truth and loads the body from .claude/commands/test.md.
  • Robust orchestration: preserves the command's stage structure, gate rules, evaluation rules, and agent binding while interpreting user prompts as arguments.

Quick Start

Invoke the /test workflow in Codex to generate unit tests for your target code

Frequently Asked Questions about azoth-test

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

FAQPage Schema
How do I auto-generate unit tests using Codex?

The /test workflow generates unit tests by interpreting user prompts as arguments and reading the command contract files, specifically commands/test/command.yaml and .claude/commands/test.md, to drive the Codex orchestrator agent.

How does the Codex command contract workflow execute?

The workflow executes by reading commands/test/command.yaml as the source of truth for execution contracts, loading the body from .claude/commands/test.md, and preserving the command's stage structure, gate rules, and evaluation rules.

Can I trigger automated unit test generation directly from the Codex CLI?

Yes, you can trigger automated unit test generation directly from the Codex CLI or UI by sending prompts that the skill interprets as arguments to execute the /test command contract workflow.

Do I need specific command contract files to use the Codex test generation workflow?

Yes, you need the commands/test/command.yaml file as the source of truth and the .claude/commands/test.md file, as the workflow reads these to satisfy the execution contract and load the command body.

What is the best way to maintain gate rules when generating tests via Codex?

The best way to maintain gate rules is to use the /test workflow, which preserves the command's stage structure, gate rules, evaluation rules, and agent binding while orchestrating the unit test generation.