tailtest

SkillFiles & storage

Generate test scenarios, write the test file, and run it for a specific source file using the tailtest R1-R15 rule layer. When the agent needs to (1) cover a file the Stop hook skipped, (2) regenerate tests after refactoring, (3) test a legacy file Codex did not modify this session, or (4) explicitly run tailtest on a named file.

Use tailtest in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add tailtest and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the tailtest skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

tailtestStart free

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/avansaber/tailtest-codex/skills/tailtest/SKILL.md and read by ahel’s review.

Generate or update tests for $ARGUMENTS.

Read the source file at $ARGUMENTS. Generate production-like test scenarios covering its public surface -- happy path, key edge cases, and failure modes at the configured depth. Write or update the test file following the tailtest Step 4 rules in AGENTS.md (correct location, correct name, style-matched to existing tests). Run the tests and report only failures; stay silent if all pass.

Treat the file as new-file regardless of its git status -- this skill explicitly requests generation even for legacy files or files the Stop hook would normally skip.

After completing, update .tailtest/session.json: add the file to generated_tests and clear it from pending_files if present.

Signals

GitHub stars
1k
Forks
316
Last commit
Oct 2026
Advanced
Item type
skill
Key
tailtest
Source
github.com/hashgraph-online/awesome-codex-plugins