rafa status

rafa status prints where the project stands in a few lines, and reads nothing it would have to change. Before any command run inside a project, rafa may print one line saying something is new since the last status; status.notice: false turns that line off.

Spends: nothing. Changes: nothing.

Reference: rafa status

Where the project stands: branch and plan, loops, pull request, board, claims and housekeeping.

rafa status

Prints one line for each of six sections. Branch: the branch checked out at the project root and the plan its feat/<stub> names, with its task counts. Loops: how many sessions are running and how many tasks are blocked, with a line under it for each running loop and each blocked task. Pull request: the branch's open pull request, whether it can be merged and its checks. Board: the Roadmap's next issue and whether it is ready, and how many issues carry spec:blocked. Claims: each claim branch on origin as last fetched, the naming.branch template with a rafa-<n> stub (feat/rafa-<n>-<slug> by default), with a line under it for each naming the store that owns the claim, the stage label on its issue and whether it is stale. Housekeeping: what rafa cleanup would list, counted per group, and how many worktrees are idle. Git, the session records, the plans and the claim branches are read first; the pull request, the board and the stage labels are read through gh under a short deadline, and nothing is fetched. A section that cannot be read is one warn line saying why, and the others are printed all the same: it exits 1 only for a config that cannot be used. With --output=json the six sections are the data of the terminal result event. Starts no session.

Examples:

• rafa status: Prints the six sections, one line each, with the running loops and blocked tasks under Loops.
• rafa status --output=json: Gives the six sections as data, each with read and its reading or the problem.

Output formats: text, json.