跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

hora-hotfix

Fix one urgent defect and ship it through six gates, giving up the acceptance review but writing down everything it gave up. Invoked directly as /hora-hotfix when a live product is broken and the normal /hora route is too slow.

openreachtech · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add openreachtech/hora-core --skill hora-hotfix

技能说明


name: hora-hotfix description: Fix one urgent defect and ship it through six gates, giving up the acceptance review but writing down everything it gave up. Invoked directly as /hora-hotfix when a live product is broken and the normal /hora route is too slow.

hora-hotfix

Fix one defect. Ship it. Write down what you skipped.

Read ../hora/references/structure.md and ../hora/references/commits.md first. This skill is read-only on specs/. It reports a spec problem; it never fixes one.

Runs at the root of the hora repository, like every other hora skill. Every git command runs in the main session.


What this skill is

/hora-build takes one feature through eighteen checkpoints. This skill takes one defect through six gates. It is not a short version of /hora-build. The unit of work is different, so the gates are different.

What it gives upreach — the acceptance review, the browser run, the UX audit, the scenario list, the version's own criteria, /hora-spec and /hora-plan
What it never gives upone failing test, the full unit suites, lint on the files it touched, the git rules, the record
Where the skipped work goes.hora/hotfix/<hotfix-id>.md, as a written debt. /hora-plan turns it back into real work later ("Paying the debt back", below)
What it changes in the normal routenothing. /hora-accept and the eighteen checkpoints are untouched, so a version's own acceptance is exactly as strict as before

This is a lever, and it follows the rule every lever follows (../hora/references/structure.md, "Where a lever lives"). It reduces work. It may not reduce verification, and it may not reduce what is recorded. A run that gave up a step pays for it in the record.


The six gates

A gate has one exit condition. Run them in order. No gate starts until the one before it is done.

GateRuns inExit condition
H1Admitthe main session, in conversationthis fix has none of the properties that stop a hotfix, or a person chose a way forward. The one sentence saying what "fixed" means is written
H2Reproducean implementer agenta test exists that fails, and it fails because of this defect
H3Fixan implementer agentH2's test passes, the change is the smallest one that does that, and lint passes on the files it touched
H4Blast radiusthe main sessionthe unit suites pass in every repository — in full, or narrowed against a stated reason and the fact it rests on — and every step this fix's touched surface forces has run
H5Recordthe main session.hora/hotfix/<hotfix-id>.md is written, and says what was skipped, which features were touched, and what happens to bad data already written
H6Landthe main sessionhotfix/<hotfix-id> is merged into main, and the catch-up is handed to /hora

The <hotfix-id> is a short kebab-case name for the defect — session-expiry-blank, not fix-1. Propose one at H1 and get it confirmed.


H1. Admit

This gate is where most of the value is. A hotfix that should have been a release is the failure this gate exists to stop.

Six properties stop a hotfix

a schema change that is not backward compatible
    (it drops, renames, narrows, or overwrites something that already exists)
a schema change touching a table that an open release/<version> also has a
    pending migration for
a change to .hora/contracts/<version>/
a dependency added, removed or updated
a new operation, screen or background job
work that does not fit one branch, so you want to cut a branch from
    hotfix/<hotfix-id>   (../hora/references/commits.md)

When one of them holds, do not refuse. Show the choices

A refusal helps nobody at three in the morning. Work out a real alternative for this defect first, then put the choices to the person (../hora/references/asking.md — this is a proposal, not a check).

1. Ship a code-only fix now  (recommend this one)
     Stop the exposure, stop the bad write, or add a guard. The destructive
     half waits for the next version. State the actual change you would make
2. Do it as a patch-bumped release/<version>
     The normal /hora route. Slower, but it gets accepted
3. A person does it outside hora            <- offer only for a destructive
     The kit does not pretend it gated this.   schema change
     Record who decided and what they did

Never work out the alternative in general terms. "There is usually a code-only version" is not usable. Name the file and the change.

The destructive half never rides on a hotfix. Option 3 exists so the work is recorded when a person decides to do it anyway. Without it, the same thing happens with no record at all.

A schema change may ride along if all three hold

1. Backward compatible — the code running in production right now still works
                         after the migration is applied
2. No loss            — nothing existing is dropped, renamed, narrowed or
                         overwritten
3. Timed              — the run time and the lock behavior are stated as
                         numbers, against the real row count

When all three hold, the migration can be applied first and the code after it, so no deploy has to be atomic.

Repairing bad rows is not a migration. A migration file replays in every environment forever. Do the repair as a one-off script a person runs and can undo from a backup, and record it under data-damage:.

Then get the one sentence

Ask the person: what has to be true for this to count as fixed? One sentence.

Never work this out yourself. It states what the product should do, which only a person may state (../hora/references/structure.md, invariant 2). That sentence is this run's whole acceptance criteria.


H2. Reproduce

**Write the test

阅读完整来源 ↗