Adversarial PR code review using Codex CLI. Codex review (~20-50 min) -> structured findings -> HITL approval -> fix loop.
원문 언어: 영어
메뉴
SkillsMP는 Soju06/codex-lb에서 13개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 13개 중 13개를 표시합니다.
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.
원문 언어: 영어