Menu
Read-only snapshot of where every issue stands, locally and on GitHub.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Finish and land the focus issue: tests, optional version bump, status update, commit, push, and PR.
Process many issues hands-off in a row: resolve a queue, then run each through the yolo chain under one up-front confirm. Stops only when input is strictly necessary.
Audit .issueflows/ for dirty conditions and optionally apply safe repairs.
Review open GitHub issues and apply labels (extendable kinds; v1: yolo).
Smart dispatcher: detect where the focus issue stands and dispatch to /iflow-init, /iflow-plan, /iflow-start, or /iflow-close.
Chain init → plan → start → close yolo for a small, low-risk issue under one consolidated confirm. Stops on any ambiguity.
| name | iflow-status |
| description | Read-only snapshot of where every issue stands, locally and on GitHub. |
| disable-model-invocation | true |
| issue-flow-version | 0.4.2a4 |
/iflow-status)Follow this skill for a bird's-eye view of every issue's status — local tracking state (focus / parked / solved) plus open GitHub issues — rather than acting on the single focus issue.
Do not use this skill to change anything. It is read-only and off-path; for acting on the focus issue use /iflow, and to choose the next issue use /iflow-pick.
Invoke: type iflow status in chat, or /iflow-status from the slash menu (iflow-status also works).
Profile: economy — Prioritize speed and token economy over deep reasoning.
In Cursor: use Auto or a fast model before invoking this step.
Keep scope tight to what this step requires.
Before any git, gh, or .issueflows/ path operation in this workflow:
Resolution order (stop when unambiguous):
root:<path>, repo:<folder-basename> (directory name, e.g. cellpy-core), or repo:owner/name.issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returned project_root and repo; pass -C <project_root> to other issue-flow agent … subcommands. When the answer came from the workspace registry, the payload sets resolved_via_workspace_default: true.^\d+- → that root..issueflows/ tree visible in the workspace → that root.issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member repo; use it when no scaffold matched above. Tell the user the default was used.After resolution, treat the result as <project_root> and <owner/repo>:
git -C <project_root> … (or issue-flow agent … -C <project_root> for supported ops).gh … --repo <owner/repo> — never rely on gh's implicit cwd default..issueflows/… paths are under <project_root>.When .issueflows/04-designs-and-guides/multi-repo-workspaces.md exists, read it for layout and cross-repo guidance.
CLI fast path (optional). If the
issue-flowCLI is onPATH, runissue-flow status(add--localto skip the GitHub query,--jsonfor a machine-readable object) — it produces this whole overview deterministically. The CLI is optional: if it is missing or errors, fall back to the manual instructions below. (issue-flowis only present when the user installed it, e.g.uv tool install issue-flow.)
Context / preflight. Detect the default branch (gh repo view --json defaultBranchRef -q .defaultBranchRef.name; fall back to git symbolic-ref --quiet --short refs/remotes/origin/HEAD | sed 's|^origin/||', else main). Report current branch, clean/dirty tree (git status --porcelain), and ahead/behind vs origin/<default>. If the branch matches ^(\d+)-.+, treat the leading digits as the focus issue N.
Focus issue (.issueflows/01-current-issues/). For the focus group, read its title from issue<n>_original.md and classify the lifecycle stage with the /iflow first-match logic:
issue<n>_original.md → /iflow-init.issue<n>_plan.md → /iflow-plan.- [x] Done unchecked → /iflow-start.- [x] Done (case-insensitive) → /iflow-close.
Report the stage and suggested next step.Parked work (.issueflows/02-partly-solved-issues/). List each issue<n>_* group: number, title, one-line status if present.
Solved archive (.issueflows/03-solved-issues/). Report the count of distinct solved issue numbers and the most recent few.
4a. In-flight cycle. If .issueflows/01-current-issues/cycle_status.md exists, a /iflow-cycle batch run is paused or active — report it and its progress (from the file's checklist), and note that /iflow-cycle resume continues it. (issue-flow status --json reports this as cycle_active.)
Open GitHub issues (skip if the user passed local). Run gh issue list --state open --json number,title,labels,milestone,updatedAt and tag each issue's local state: focus, parked, solved-locally, or untracked. If gh is missing/unauthenticated, skip this section and note it (suggest gh auth login) — never fail.
Summary line. One terse line, e.g. Focus: #20 (start). Parked: 2. Solved: 31. Open on GitHub: 7 (5 untracked).
.issueflows/ and runs read-only git / gh queries./iflow, /iflow-start, or /iflow-close.gh, no network, or an empty .issueflows/ must still yield a useful local report.