CRW

Plugin crw in thisisjun786/codex-relay-workflow. Commands read from the repo's manifest — 26 days ago.

Skills (31)

• crw-add-issue

  Turn one short request into one ready tracking issue that passes the release gate. Use for 'add an issue', a one-paragraph bug or change request, or a finding to register; crw-plan decomposes a goal into projects and issues.

• crw-ast-grep

  AST-aware code search and rewrite with ast-grep (sg) across 25 languages: structural matches and deterministic codemods such as every call, import or class shaped like X, console.log to logger.info, YAML rules. Use rg for string contents, comments and filenames.

• crw-canon

  Reference index for the rules that more than one CRW skill reads: the levels, the tracking model, the release gate, the schedule contract, delivery, execution roles, design explanation, repository governance and the skill family. Never invoked by itself; other skills link to its files.

• crw-check

  Check delivered work against the canonical tracking documents and issue criteria, find contradictions between specifications and evidence, and judge progress against the schedule. Use for requirement drift, completion and invariant audits; crw-run executes, crw-qa drives a surface by hand.

• crw-continue

  Use to continue one task to its authorized completion condition. Bare crw-continue means HOTL; explicit explanation, interview-only, plan-only, read-only, or HITL limits win. A milestone request goes to crw-run. Triggers: crw-continue, continue until done, HOTL, 끝까지 해줘, docs-first.

• crw-define

  Settle a milestone and its issues before they are registered in the tracking repository: purpose, desired change, success evidence, scope and open decisions, and whether a question is really needed. Hand the agreed definition to crw-plan. Triggers: 마일스톤 정의, 요구사항 정리, 아이디어 정리.

• crw-dev-architecture

  Module boundary work: circular dependency detection, coupling review, barrel or re-export changes and validation placement. Triggers: circular import, module split, layer violation, dependency direction, utils growth, barrel file, boundary review, 모듈 경계, 순환 참조.

• crw-dev-backend

  Backend, API, server and database work: API design, architecture, database optimization, error handling, middleware, observability, queues, long-lived connections. Triggers: backend, API, REST, GraphQL, schema, migration, query optimization, middleware, OTel, caching, 백엔드, 마이그레이션, 쿼리 최적화.

• crw-dev-code-reviewer

  Independent code review of a diff or pull request: review process, quality thresholds, antipatterns, verdicts and test auditor gates. The author side of requesting and receiving feedback is crw-dev. Triggers: code review, PR review, check my diff, before merge, antipattern, 코드 리뷰, 머지 전에 확인.

• crw-dev-data

  MUST USE for data engineering and analysis work — pipelines, ETL/ELT, data quality, SQL optimization, schema evolution, backfills, and reporting. Triggers: ETL, ELT, pipeline, data quality, SQL optimization, backfill, migration, schema drift, validation, batch vs streaming, 데이터 파이프라인, 데이터 품질, 백필.

• crw-dev-debugging

  Root-cause debugging in any language: crashes, silent failures, wrong output, build or test failures, flaky tests, performance regressions; also system behaviour analysis of an unknown app, API or tool. Triggers: debug this, why is X failing, root cause, how does X work, figure out how, 디버깅, 로직 파악.

• crw-dev-devops

  DevOps and delivery: container builds, deploy pipelines, Kubernetes, IaC, SRE, edge/serverless, ML infra, native desktop acceptance, stale-branch hygiene, stacked-PR CI in repositories that use PRs. Triggers: Dockerfile, deploy, CI/CD, Terraform, SLO, stale branch, branch cleanup, 배포, 인프라.

• crw-dev-frontend

  Frontend and web UI implementation: building, styling or redesigning pages and components, responsive layouts, motion, component architecture. Implements the direction chosen with crw-dev-uiux-design. Triggers: frontend, UI, component, CSS, responsive, animation, React, Tailwind, 프론트엔드, 반응형.

• crw-dev-scaffolding

  Project setup, feature scaffolding, structural audits and source-of-truth docs: feature-based layout, colocation, boundary exports, repo-first convention reuse. Triggers: scaffold, scaffolding, new project, new feature, add module, monorepo setup, API docs, 스캐폴딩, 새 프로젝트, 모듈 추가.

• crw-dev-security

  MUST USE for security guidance covering XSS, CSRF, SQL injection, JWT, OAuth, secrets, OWASP, auth hardening, supply chain, and threat model work. Activates for security-sensitive code, trust boundaries, PII, uploads, payments, CI integrity, tool-using agents, or security/threat_model task tags.

• crw-dev-testing

  Automated test strategy: unit, integration, API, contract, Playwright E2E, CI gates, coverage and TDD. Driving a built surface by hand is crw-qa; the reviewer's test gates are crw-dev-code-reviewer. Triggers: write tests, regression test, Playwright, E2E, contract test, coverage, 테스트, 회귀 테스트.

• crw-dev-uiux-design

  UI/UX direction and design judgment: vague visual briefs, onboarding, empty, error and loading states, layout, typography, favicons, logos, brand identity. Hands the chosen direction to crw-dev-frontend. Triggers: make it look good, modern, clean, onboarding, empty state, favicon, logo, 깔끔하게, 모던하게.

• crw-dev-visualizer

  Visual documents: HTML reports, SVG diagrams, charts, interactive explainers, infographics and PDF deliverables. Triggers: visualize, architecture diagram, comparison report, infographic, 시각화, 그려줘, 보고서, PDF 생성. Text-only requests and ordinary code changes need no visual.

• crw-dev

  Class-scaled development guidelines: classify the task C0-C5, keep the safety rules and fresh proof, and load the matching crw-dev-* surface owner. Use for coding, fixes and docs in a repository; project coordination and tracking planning go to crw-run and crw-plan. Triggers: develop, fix, docs, 개발.

• crw-kwrite

  Korean prose polishing (윤문): revise existing Korean text so it reads as written by a person, removing translationese and AI idioms, fixing register breaks and varying rhythm while keeping the meaning exact. Triggers: 윤문, 다듬어줘, 자연스럽게, 매끄럽게, 교정, AI투, 번역투, Korean polish, kwrite.

• crw-plan

  Decompose an agreed goal into milestones (projects) and issues, each issue one concept bundle. Use for product planning, a roadmap or 기획, and scoped plan updates. Settling an unclear milestone before registration is crw-define's, dispatch crw-run's, drift crw-check's.

• crw-qa

  Manual QA of a built surface (web UI, TUI, CLI, HTTP API, desktop GUI): drive it for real, capture artifacts, probe adversarial inputs, record teardown. Suites are crw-dev-testing; delivery against the issue criteria is crw-check. Triggers: manual QA, QA this, smoke test, visual QA, 수동 QA, 직접 돌려봐.

• crw-recall

  Search past Codex session history and the memory store from the CLI when a term from prior work is unfamiliar or context was lost after a compact or restart. Triggers: recall, past session, chat search, memory search, last time, 지난 세션, 지난번, 기억나?

• crw-refactor

  Diagnose structural debt after a cycle, project or sprint from verified delivery and actual code changes. Read-only: recommends up to three bounded repairs, and a chosen one is added as a tracking issue by crw-add-issue. Use for post-cycle refactoring, duplication or compatibility cleanup.

• crw-repo-map

  Use RepoMap for codebase overview, structure maps, symbol overview, and architecture map exploration. Triggers: repo map, codebase overview, structure map, 와꾸, project structure, unfamiliar codebase exploration, symbol overview, architecture map.

• crw-run

  Coordinate one milestone as its child: bind, dispatch, observe, verify, correct, integrate and resume; no goal by default, resumed by a relay event. Also the parent's project order, decisions, reports and 중간점검.

• crw-search

  Web search for external, current or public information: latest versions, news, prices, docs, status, X/Twitter, and deep research with a cited report; Luna fan-out for broad parallel discovery. Triggers: search, look up, latest, news, deep research, 검색, 웹검색, 딥리서치, 루나검색.

• crw-status

  Read-only report of where work stands, by layer from the parent to each issue, with the evidence, and the one next action when asked. Use for '현재 어디까지 됐어?', '상황 알려줘', '다음에 뭐 하지?'. crw-check audits delivery against criteria; crw-run executes.

• crw-tidy

  Diagnose, read-only, which documents and issues fall short of already-agreed authoring and management rules; Supplement the clear gaps only as the owner of that body. Use for a rule-conformance sweep or tidy pass; crw-check owns delivery and contradictions, crw-plan the rules themselves.

• crw-work

  Use for class-scaled work and completion evidence on one task. Explicit explanation, interview-only, plan-only, and read-only limits win; loading the skill does not activate execution or continuation. Triggers: task work, 단계별로.

• crw-worktree-guardian

  Codex-app managed worktrees (hash-named dirs under ~/.codex/worktrees, detached HEAD, thread-bound workspaces): adopt in place with git switch -c or branch -m, never delete and recreate. Triggers: worktree, 워크트리, rename worktree, detached HEAD worktree.

Similar plugins