Adversarial PR code review using Codex CLI. Codex review (~20-50 min) -> structured findings -> HITL approval -> fix loop.
原文语言:英语
菜单
已展示 13 / 13 个已收集 Skill。
Adversarial PR code review using Codex CLI. Codex review (~20-50 min) -> structured findings -> HITL approval -> fix loop.
原文语言:英语
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
原文语言:英语
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
原文语言:英语
Archive multiple completed changes at once. Use when archiving several parallel changes.
原文语言:英语
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
原文语言:英语
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
原文语言:英语
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
原文语言:英语
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
原文语言:英语
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
原文语言:英语
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
原文语言:英语
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
原文语言:英语
Project code conventions reference. Covers typing, structure, DI, testing, and anti-pattern rules for module implementation.
原文语言:英语
OpenSpec context documentation policy: keep requirements in spec.md and capture narrative context in context/overview/rationale docs under openspec/specs. Use when creating or updating OpenSpec docs, spec context, or onboarding/guide documentation.
原文语言:英语