maintain
Route alerts, CI or regression failures, or dogfood incidents into an intent. Use for incidents outside an active unmerged change that arrive without a user's request to fix a bug; that request starts at the entry station.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- maintain
- version
- 1.1.0
- description
- Route alerts, CI or regression failures, or dogfood incidents into an intent. Use for incidents outside an active unmerged change that arrive without a user's request to fix a bug; that request starts at the entry station.
02 资源文件 1
- 参考文档README.md1.4 KB
03 SKILL.md 正文
Maintain
Maintenance changes how work enters Loom, not how it is published. An active unmerged change's CI failure stays with that change and follows Ship's continuation contract instead of entering Maintain.
When conflicting failure reports or an unverified premise could change incident
intake, identify that decision and use loom-code:engineering-research as needed.
Reuse adequate evidence directly; return findings or uncertainty to this intake
without implementing a fix, replacing intent capture or expanding authorization.
- Reproduce the incident. Reuse an existing test that exposes the root cause, or capture the smallest permanent regression case when coverage is missing.
- Attach it to the matching open intent, or create one with
originator: maintenance-loopwhen none exists. - Record which existing check should have caught it. Add a new mechanism only when a deterministic regression test earns its ongoing cost.
- Hand the confirmed intent to Write Plan and continue through Build, one closing Review, generated attestation, and fast Ship.
Do not create review rounds, dispatch records, probe ledgers, or SHA alignment work during incident intake.
04 同仓库更多 Skills
using-loom-workflow
Route broad Loom workflow-tool requests to the right skill. Use when the request spans tools or the right workflow skill is unclear.
skill-retro
Review selected past or current Claude Code or Codex sessions against readable target skill sources and related integration. Produce source-linked proposals without applying changes.
recap-state
Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in /recap is an away-summary.
project-retro
Review one current or specified coding session for source-backed project development improvements. Use for a requested retrospective, including 振り返り seeking improvements; not for current-progress recaps or recurring skill mining.
loom-visualization
Show comparisons, flows, decisions, states or reasoning chains as tables, ASCII or Mermaid in coding chat, including when a Loom station reports to the user (intent restatement, choices, acceptance test results); not Obsidian notes.
loom-memory
Record repo-wide lessons when saving to your own memory or asked to remember; recall, reconcile, or forget them when a task needs it.