flight

Plugin flight from marketplace flightdirector in AICrafting/FlightDirector. Commands read from the repo's manifest — 1 month ago.

Skills (10)

• add-an-issue-tracker

  Use when connecting an issue tracker to flight — "add an issue tracker", "add another tracker", "connect Jira", "track issues on GitHub too", "public issues come in on GitHub", "set up the tracker labels", "fix the tracker token" — when setting-up-a-repo needs the repo's first tracker, or when a con

• cleaning-up-branches

  Use when clearing out branches whose work has already shipped — "clean up the branches", "delete merged branches", "prune old feature branches", "what branches can go", "tidy up the worktrees", "origin is full of old feature branches". Finds feature/bugfix/release/batch branches already merged into

• copying-an-issue

  Use when copying an issue from one configured issue tracker to another, or bringing an earlier copy up to date — "copy FJ-12 to GH", "pull GH-3 into Forgejo", "put this on Jira too", "move this issue over to the public tracker", "resync the copy", "bring the GitHub copy up to date". Copies the title

• filing-issues

  Use when the user invokes `/issue <description>`, or says "file an issue", "open a ticket", "track this", "add an issue for that", "create an issue", "log a bug" — even if the description is terse or vague. Also use when an existing issue's title/body is now stale and needs updating, or a comment sh

• promoting-a-branch

  Use when advancing the current branch to the next stage — "promote this", "promote to qa", "promote develop to main", "open a PR for this branch", "this branch is ready". Moves the current branch one hop up the configured stages pipeline (e.g. feature → develop → qa → main), applying that hop's merg

• promoting-branches

  Use when promoting several first-hop feature branches at once — "promote each zone", "promote the first zone", "promote issues 18, 93, 12", "promote all to-test", "batch promote", "ship the batch". Promotes a selected group of feature branches into stages[0], honoring that hop's merge strategy (dire

• queue-batches

  Use when the user invokes `/queue-batches`, `/queue-batches NxM` (e.g. `3x5`), or says "queue up some batches", "kick off parallel work on some issues", "run N groups of M issues in parallel". Dispatches N background agents in isolated git worktrees, each working M issues sequentially through the wo

• setting-up-a-repo

  Use when setting up a repo for flight for the first time — "set up this repo", "set up flight", "configure flight", "set up labels", "bootstrap labels", "add the default labels" — when filing/triage reveals the repo has no flight config or few labels, when re-running setup after an upgrade to pick u

• triaging-issues

  Use when the user asks what to work on next — "what should I work on", "what's next", "any quick wins", "show me the open issues", "what's in the backlog", "pick something to do". Lists and filters open issues for selection. Read-only — it never creates or modifies anything.

• working-an-issue

  Use when starting, progressing, or finishing work on a specific issue — "let's work on #N" (or a tracker-qualified id like GH-12 / PROJ-7), "start issue #N", "I'll take #N", "this is ready to test", "merge #N", "close out #N". Drives the per-issue branch → status-label → test → merge → finish lifecy

Slash commands (1)

• /flight:version

  Show which flight plugin is loaded — its version, install and root — and whether the `flight` CLI on PATH matches

Hooks (3)

• UserPromptSubmit

  LS_HARNESS=claude "${CLAUDE_PLUGIN_ROOT}/bin/flight" prompt-log prompt

• Stop

  LS_HARNESS=claude "${CLAUDE_PLUGIN_ROOT}/bin/flight" prompt-log stop

• SubagentStop

  LS_HARNESS=claude "${CLAUDE_PLUGIN_ROOT}/bin/flight" prompt-log subagent-stop

Similar plugins