AGENT SKILL

reach-bug

The bug flow for one slice: the smallest fix, proven by the same run, without git. Use when a check or qualification fails; a grade comes back with a failed case; the student says something is broken or gives the wrong answer. rEach also tells you when to load it. Not for new behaviour the student wants: use the reach-feature skill.

License 许可
MIT
所属仓库
SteveBenner/rEach
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
reach-bug
description
The bug flow for one slice: the smallest fix, proven by the same run, without git. Use when a check or qualification fails; a grade comes back with a failed case; the student says something is broken or gives the wrong answer. rEach also tells you when to load it. Not for new behaviour the student wants: use the reach-feature skill.

03 SKILL.md 正文

The bug flow for one slice: the smallest fix, proven by the same run. Work the steps in order. Never run git or start a repository; overwrite files in place and use reach checkpoint as the history.

  1. Name it exactly. The QF code and scenario name from reach qualify, the finding id and file from reach check --format agent, the failed case on a grade receipt, or the student's own description of the wrong answer. Quote it word for word in your notes; tell the student about it only in business terms.
  2. Reproduce it with the same command before changing anything. A wrong answer the student reports: write a scenario under qualify/features that shows it and watch it fail. For QF-UNCOVERED, read the returned steps.coverage.rows and next: behavior checks have not run yet, and the assistant owns the missing technical scenarios. The student's explanations and contributions remain their own work.
  3. reach checkpoint save --note "before fix: <name>".
  4. Show it in a scenario. Add or correct the scenario that captures the case, with the slice's tag, so the fix is proven and stays proven. For QF-UNCOVERED, write a scenario for each missing name, with exactly that name and tag, from the agreed plan and course contract. Ask the student only for a business expectation that is still missing. Follow the ladder's current limits and stop conditions; continue to the requalification step instead of finishing with a readiness summary.
  5. The smallest fix in the owned files, reading each file before you overwrite it. Do not rewrite a file or fix things that were not named.
  6. reach check --format agent, then reach qualify.
  7. Follow the ladder reach qualify prints (the TOZERO directive). When findings grow instead of shrinking, reach checkpoint restore <n> to the last good one and report.
  8. Passed: reach checkpoint save --note "fixed: <name>" and tell the student in at most four plain lines what now works, with their case.

04 同仓库更多 Skills

SteveBenner
SteveBenner/rEach

reach-uninstall

Remove rEach with one command the student decides on. Use when the student asks to uninstall, remove or delete rEach, or to start over without it. Not for a problem with rEach that the student wants fixed, not removed: use the reach-help skill. Not for starting over with a fresh copy of rEach: use the reach-reinstall skill.

★ 1
SteveBenner
SteveBenner/rEach

reach-submit

Hand in a slice or written work, make a ZIP of the work, and answer whether a submission was received. Use when the student wants to submit or hand in their work, or submit it again; the student asks whether a submission was received; the student wants a ZIP of their work. rEach also tells you when to load it. Not for keeping progress safe without handing it in: use the reach-checkpoint skill.

★ 1
SteveBenner
SteveBenner/rEach

reach-storage

Report and compact the memory rEach keeps on this computer, after the student's yes. Use when the student asks how much space rEach uses or wants to free space. rEach also tells you when to load it.

★ 1
SteveBenner
SteveBenner/rEach

reach-sidecar

Bring work done in the offline rEach Sidecar folder into rEach. Use when the student says they worked in the rEach Sidecar, the offline packet or the reach-sidecar folder, or has a bundle ZIP from it.

★ 1
SteveBenner
SteveBenner/rEach

reach-reinstall

Reinstall rEach with one command the student decides on: it removes rEach and installs the current stable release. Use when the student asks to reinstall rEach or to start over with a fresh copy; the student wants rEach repaired by removing it and installing it again. Not for removing rEach for good: use the reach-uninstall skill.

★ 1
SteveBenner
SteveBenner/rEach

reach-reclaim

Bring back older memory, notes or course folders from an earlier rEach install or another reach-work folder, after the student's yes. Use when the student asks to bring back, find or recover memory or work from an earlier rEach install, a set-aside folder or another reach-work folder. Not for an earlier version of the slice the student is working on: use the reach-checkpoint skill.

★ 1