fix-status

fix-status is a command for Claude Code from ThibautBaissac/rails_ai_agents. It costs 13 tokens per session (645 once invoked), scanned A, original, MIT.

A command for listing and reviewing separate Git worktrees created for Sentry fixes. A worktree is an additional working directory connected to the same Git repository.

In plain words
What is it for?
Use it to inspect active Sentry fix branches, their latest commits, changed files, and current status.
Why use it?
It shows which fixes are still being worked on and which have produced a completed commit. It also provides actions for merging or discarding those branches.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to inspect active Sentry fix branches, their latest commits, changed files, and current status.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thibautbaissac/rails_ai_agents/fix-status
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.

Clone the repo
git clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fix-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/fix-status/github.svg)](https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/fix-status)
Your own site
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/fix-status"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/fix-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for fix-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/fix-status"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/fix-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 645 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00013 $0.00645
Opus 5.5 $0.00005 $0.00258
Sonnet 5.5 $0.00003 $0.00129
Haiku 4.5 $0.00001 $0.00064

Measured 2mo ago against content hash 8e543d0392b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fix-status 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 2mo 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/sentry/fix-status.md · 62 lines

How it starts

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

Fix Status: Review Active Fix Branches

List all active fix branches created by /sentry:fix-error, show their status, and manage them (merge or discard).

Workflow

  1. List worktrees: Run git worktree list and parse the output.

  2. Filter fix branches: Keep only worktrees whose branch name matches fix/SENTRY-*.

  3. For each fix worktree, gather:

    • Branch name: from the worktree list output
    • Worktree path: the filesystem path
    • Latest commit: Run git -C {worktree_path} log -1 --oneline to get the last commit message
    • Files changed: Run git -C {worktree_path} diff --stat HEAD~1 HEAD 2>/dev/null (if a commit exists)
    • Status: Determine based on:
      • If a commit with fix: prefix exists → "Complete"
      • If no new commits beyond the branch point → "In progress" (agent may still be working)
  4. Present results as a markdown table:

    ## Active Fix Branches
    
    | Branch | Status | Last Commit | Files Changed | Actions |
    |--------|--------|-------------|---------------|---------|
    | fix/SENTRY-PROJECT-123-nil-check | Complete | fix: TypeError (Sentry PROJECT-123) | 2 files | merge / discard |
    | fix/SENTRY-PROJECT-124-timeout | In progress | — | — | wait |
    
  5. Handle developer actions: If the developer asks to merge or discard:

    Merge:

    1. Run git merge {branch_name} from the main working tree

    2. If merge succeeds: run git worktree remove {worktree_path}

    3. If merge conflicts: report the conflicts and let the developer resolve manually

    4. Suggest resolving the Sentry issue:

      Fix merged. Resolve this issue in Sentry?
      Use: /sentry:resolve {issue_id}
      

      Extract the issue ID from the branch name (fix/SENTRY-{short_id}-*).

    Discard:

    1. Run git worktree remove {worktree_path} --force
    2. Run git branch -D {branch_name}
    3. Confirm: "Worktree and branch {branch_name} have been removed."
  6. If no fix worktrees exist: Report "No active fix branches found. Use /sentry:fix-error to launch a fix."

Read the full file on GitHub · 62 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. 2mo ago First seen · 62 lines · 13 tokens per session scan A 8e543d0392b0

Subscribe to this mod's changes

fix-status is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 645 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

fix-status compared with commands from other repositories

fix-status next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
fix-statusThibautBaissac/rails_ai_agentsCommand6725mo agoMITA13Claude Code
barista-fixfrappe/frappe-uiCommand1.1k2d agoMITA17Claude Code
fix-issueyonatangross/orchestkitCommand299yesterdayMITA45Claude Code, Cursor
unbloatathola/claude-night-marketCommand348yesterdayMITA27Claude Code
payload-revertopenshift-eng/ai-helpersCommand122yesterdayApache-2.0A12Claude Code
AGENTSmax-sixty/worktrunkCommand12kyesterdaynoneA0Claude Code
fix-issuefltman/project-scaffolderCommand889d agoMITA0Claude Code