fix-a-bug
Have a Rush cloud agent reproduce a bug, fix it and open a pull request with a test. Use when someone shares an error, a stack trace, a failing test or CI run, or a bug report or issue and wants it fixed in a repository.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- fix-a-bug
- description
- Have a Rush cloud agent reproduce a bug, fix it and open a pull request with a test. Use when someone shares an error, a stack trace, a failing test or CI run, or a bug report or issue and wants it fixed in a repository.
03 SKILL.md 正文
Fix a bug with Rush
- Gather what the agent needs. The session cannot see this conversation or the person's machine, so collect: the repository, the exact error or stack trace, how to trigger it, what should happen instead, and any file, commit or CI link already suspected. Paste an issue's text rather than only its link. Ask one question if the repository or the symptom is missing.
- Start it. Call
create_sessionwith the repository (or the branch the bug is on) asrepo, a fresh UUID you write yourself asrequest_id, and atasklike: "Fix this bug. <symptom, error, steps>. First reproduce it and write a test that fails because of it. Then fix the cause, not the symptom, and run the test suite. Open a pull request that explains the cause, the fix and the test, and do not merge it. If you cannot reproduce it, stop and report what you tried." Leave out "do not merge" only when the person asked for a merge. - Wait with
wait_for_sessions(timeout_seconds: 50) until it settles; a fix takes several minutes. - Report. From
get_session: the cause in a sentence or two, the pull request link (a merge request on gitlab.com), and whether the new test failed before the fix and passes after.get_session_changeswithinclude_diffshows the change when the person wants to read it here. If it could not reproduce the bug, give what it tried and ask for the missing detail. - Iterate in the same session. Review comments or a red check go back
with
send_session_message("CI fails on lint: fix it and push"), so the agent keeps its computer and context and updates the same pull request.
Refusals: see hand-off-a-task under "When Rush refuses".
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.