bx-dev는 광고-호크 개발 세션을 위한 자체 유지된 Codex 기술입니다. 세션 지점. 구현을위한 단일 샷 코덱 서브 시약을 조정, 리뷰, 옵션 QA, git commits, PR 작성, 합병 및 정리.

이것은 무엇인가?

bx-dev는 Codex와 정상적인 git 저장소에서 작업할 수 있는 워크플로 기술입니다. 임시 개발 세션을 시작하고, 세션에 고립 된 작업을 유지 분기, Codex subagents에 구현 및 검토를 위임하고, 당신을 도울 결과를 PR을 통해 dev로 밀어.

직접 Codex 대신 구조화 코딩 세션을 원할 때 사용하십시오. 편집. 이 기술은 특히 기능 작업, 버그 수정, 복원, 또는 구현, 검토, 커밋 및 옵션이 원하는 다중 단계 변경 QA는 하나의 워크플로에서 처리됩니다.

이 저장소는 앱 템플릿이 아니며 프로젝트의 수정을 하지 않습니다. 기타. Codex에 $bx-dev 기술만 추가합니다.

당신이 그것을 사용하는 방법

Codex 설치 및 재시작 후, 저장소에 Codex를 엽니다. 작업하고 같은 메시지를 가진 세션을 시작:

그런 다음 같은 Codex 채팅에서 작업을하십시오.

일반 세션 명령:

bx-dev Skill for Codex

bx-dev is a self-contained Codex skill for ad-hoc development sessions on a session branch. It coordinates single-shot Codex subagents for implementation, review, optional QA, git commits, PR creation, merge, and cleanup.

What This Is

bx-dev is a workflow skill for working on a normal git repository with Codex. It starts a temporary development session, keeps the work isolated on a session branch, delegates implementation and review to Codex subagents, and helps you push the result back into dev through a PR.

Use it when you want a structured coding session instead of one direct Codex edit. The skill is especially useful for feature work, bug fixes, refactors, or multi-step changes where you want implementation, review, commits, and optional QA handled in one workflow.

This repository is not an app template and does not modify your project by itself. Installing it only adds the $bx-dev skill to Codex.

How You Use It

After installing and restarting Codex, open Codex in the repository you want to work on and start a session with a message like:

$bx-dev auth-cleanup

Then give tasks in the same Codex chat:

fix password reset validation
add tests for the reset token edge cases
push
exit

Common session commands:

• push — run detected checks, push the session branch, create a PR to dev, and merge it when the push and merge gates pass.
• exit — finish the session: commit leftover work when appropriate, push and merge unpushed commits, switch back to dev, clean session state, and delete the session branch when it is safe. If tests, PR creation, or merge gates fail, exit aborts and leaves the session intact.
• set dev-server — record a running browser URL for QA when using --careful. It does not start the server.

Supported flags:

• $bx-dev --careful — add a QA phase after implementation and review. For web UI work, start your dev server yourself and provide its URL when the skill asks, or later with set dev-server .
• $bx-dev --solo — run without subagents; useful for small changes. Solo mode still uses the session branch and creates its commit on push.
• $bx-dev --no-review — skip review in team mode.
• $bx-dev --plan-approve — ask for your approval after the scout plan before implementation starts.
• $bx-dev --no-sop — use a regular PR merge instead of the default squash merge on push.
• $bx-dev --sop — accepted for backward compatibility only; squash is already the default.

$bx-dev messages are Codex prompts, not terminal commands. Run terminal commands only where the README explicitly shows shell snippets.

What Happens In A Session

At a high level, bx-dev:

1. Checks that the current repo is clean enough to start.
2. Ensures origin/dev exists, then creates a session branch from it.