takeoff

A workflow step that rebases a branch onto develop, pushes it to the remote repository, and creates a pull request.

In plain words
What is it for?
Use it with an issue ID to run the earlier workflow stages when needed, rebase the work, push the branch, and open a pull request.
Why use it?
It collects the remote publishing actions needed to submit completed work for review.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/circui-try/circuit/takeoff
Clone the repo
git clone --depth 1 https://github.com/CIrcui-try/Circuit

Made for: Claude Code.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,332 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.01332
Opus 5 $0.00013 $0.00666
Sonnet 5 $0.00005 $0.00266
Haiku 4.5 $0.00003 $0.00133

Measured 2d ago against content hash 0c695bfda22c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

takeoff scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/takeoff.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

이륙 시퀀스의 4단계 (Takeoff). develop 위에 리베이스하고 리모트에 push 한 뒤 PR 을 생성한다. 이 단계만 원격에 영향을 준다. 성공하면 임시 상태 파일(.claude/state/<ISSUE>.*) 을 모두 삭제한다.

$ARGUMENTS 형식: <ISSUE-ID> [--force]. 예: /takeoff CIR-15.

인자 파싱

  1. --force 분리. 첫 토큰을 <ISSUE> 로.
  2. <ISSUE> 없으면 사용법 안내 후 중단.

상태 파일 경로

  • MAIN_REPO_ROOT = $(git rev-parse --path-format=absolute --git-common-dir | xargs dirname)
  • STATE_FILE = $MAIN_REPO_ROOT/.claude/state/<ISSUE>.json
  • ISSUE_FILE = $MAIN_REPO_ROOT/.claude/state/<ISSUE>.issue.md
  • PLAN_FILE = $MAIN_REPO_ROOT/.claude/state/<ISSUE>.plan.md

자동 체이닝

상태 파일을 읽어 다음 순서로 실행:

  1. STATE_FILE 이 없으면 다른 .claude/state/*.json 을 후보나 캐시로 사용하지 않는다. 사용자가 입력한 <ISSUE> 를 정답으로 보고 /boarding <ISSUE> [--force] 를 먼저 실행한 뒤 STATE_FILE 을 다시 읽는다. 그래도 없으면 boarding 실패로 보고 중단한다.
  2. boarding.done_at == null 이거나 --force/boarding <ISSUE> [--force]. 채워져 있으면 스킵 메시지 한 줄.
  3. door_closing.done_at == null 이거나 --force/door-closing <ISSUE> [--force]. 채워져 있으면 스킵.
  4. taxiing.done_at == null 이거나 --force/taxiing <ISSUE> [--force]. 채워져 있으면 스킵.
  5. 본 단계 진행.

자동 체이닝은 본 단계까지만 — landing 은 자동으로 호출하지 않는다.

자기 단계 실행 절차

  1. 스킵 판정: takeoff.done_at 이 채워져 있고 --force 가 없으면 종료. (다만 takeoff 성공 후 상태 파일은 삭제되므로 보통 이 케이스는 발생하지 않음.)
  2. 워크트리 진입: worktree_path 로 cd. 경로가 없으면 사용자에게 안내 후 중단.
  3. 상태 점검: git status 가 깨끗한지 확인. 미커밋 변경이 있으면 사용자에게 알리고 중단.
  4. 티켓 상태 동기화: Linear 이슈가 Done/Canceled 가 아니면 상태를 In Progress 로 직접 변경한다.
  5. GitHub 인증 확인: gh-auth-check 스킬로 GitHub CLI 로그인 상태와 active account 를 확인한다.
  6. develop 리베이스: git fetch origin develop && git rebase origin/develop. 충돌 시 자동 해결 시도하지 말고 사용자에게 위임 후 중단.
  7. 푸시:
    • 첫 push: git push -u origin <branch>.
    • 리베이스로 히스토리가 바뀌었고 리모트에 이미 같은 브랜치가 있으면 사용자 승인 후 git push --force-with-lease origin <branch>.
    • develop/main 으로의 직접 푸시는 금지.
  8. PR 생성: gh pr create --base develop --head <branch>.
    • 제목: <ISSUE> <type>: <English summary> 예) CIR-15 fix: prevent white screen when adding waitlist entries.
    • 제목과 본문은 반드시 영어로 작성한다. 한국어를 쓰지 않는다.
    • 본문: HEREDOC 으로 다음 형식. 모든 placeholder 내용도 영어로 쓴다.

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 80 lines · 25 tokens per session scan A 0c695bfda22c

Subscribe to this mod's changes

takeoff is a command published in the GitHub repository CIrcui-try/Circuit (5 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,332 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.