Skip to content

tvproductions/gzkit / .agents/skills/gz-how

gz-how

Verified

Use when the operator asks "how do I …?" or "what can I …?", or when unsure which skill applies or two look alike.

references/defects-and-ghis.md

View on GitHub
# Defects and GHIs

An on-ramp: work that arrives as a finding rather than a plan. You are here when
something is wrong, drifted or missing.

## Steps

1. **Route it** by `AGENTS.md` § Defect-fix routing:
   - small, one surface, surfaced in flight, covered by a unit test → fix it
     directly, a `fix(<scope>): …` commit with a `Task:` trailer;
   - an authored OBPI brief owns the surface → report the brief and wait for
     the operator's ruling;
   - otherwise → file it.
2. **File it.** **`ghi-author`** — prior-art lookup first, then an issue with
   evidence and a closure contract. From an adopter repository, a defect in gzkit
   itself goes through **`gz-issue-file`**.
3. **Rank the queue.** **`ghi-triage`** reads every open issue and orders them.
4. **Fix and close.** **`ghi-close`** does the work, verifies it and closes the
   issue citing the commit. A GHI authorizes direct repair; it needs no ADR.

## Branches

- **The operator corrected you in flight** → **`gz-insights-remember`** records
  the course-correction before the corrected work completes.
- **A discovery or defect to note, not fix now** → `gz-insights-remember`.
- **The finding is a whole missing capability** → a pool ADR; see
  [Idea to ADR](idea-to-adr.md).
- **The gap is in a shipped surface's intent** → it is a correction under its
  owning ADR, not an enhancement.

## Only you can

Select which issue is worked next, and rule where routing is unclear.

## Then

[Commit and sync](commit-and-sync.md); later, [Release](release.md) collects the
closed issues.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall