agent-doc-discipline
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and…
@yeachan-heoInstall SkillAgent Orchestration
Skill
/verify
Verify that a change really works before you claim completion
Claude Code
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill verify --agent claude-code
Codex
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a codex -y
Cursor
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a cursor -y
Gemini CLI
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a gemini-cli -y
GitHub Copilot
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a github-copilot -y
OpenCode
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a opencode -y
Windsurf
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a windsurf -y
SKILL.md
verify.SKILL.mdname: verify description: Verify that a change really works before you claim completion
Verify
Use this skill when the user wants confidence that a feature, fix, or refactor actually works.
Goal
Turn vague “it should work” claims into concrete evidence.
Workflow
1. Identify the exact behavior that must be proven. 2. Prefer existing tests first. 3. If coverage is missing, run the narrowest direct verification commands available. 4. If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence. 5. Report only what was actually verified.
Verification order
1. Existing tests 2. Typecheck / build 3. Narrow direct command checks 4. Manual or interactive validation
Rules
- Do not say a change is complete without evidence.
- If a check fails, include the failure clearly.
- If no realistic verification path exists, say that explicitly instead of bluffing.
- Prefer concise evidence summaries over noisy logs.
Output
- What was verified
- Which commands/tests were run
- What passed
- What failed or remains unverified
Ships withoh-my-claudecode
For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.
41k84 skills21 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 40.7k
Other skills on oh-my-claudecode.
@yeachan-heoInstall Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
@yeachan-heoInstall Skillarchitect
Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API surface and…
@yeachan-heoInstall Skillarchitecture-survey
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical…
@yeachan-heoInstall Skillarena
Run N parallel candidates at one brief and synthesize: rubric-first framing, isolated fan-out, a cross-judge on a different…
@yeachan-heoInstall Skillask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on…
@yeachan-heoInstall SkillMore skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
@paperclipaiInstall Skilladr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
@ruvnetInstall SkillQuestions about verify.
- Which coding agents can use verify?
- verify installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.