e2e-lifecycle-tombstone
E2E fixture skill (HATS-1147). Declares the RETIRED lifecycle_hooks channel so the retirement e2e can prove that composition fails loudly through the real ai-hats binary instead of silently ignoring the declaration. Not shipped.
- License 许可
- MIT
- 所属仓库
- muratovv/ai-hats
- 最近更新
- 2026-11-05
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- e2e-lifecycle-tombstone
- ai_hats
- { "lifecycle_hooks": { "plan--execute": [ "hooks/gate.sh" ] } }
- description
- E2E fixture skill (HATS-1147). Declares the RETIRED lifecycle_hooks channel so the retirement e2e can prove that composition fails loudly through the real ai-hats binary instead of silently ignoring the declaration. Not shipped.
02 资源文件 1
- 脚本hooks/gate.sh257 B
03 SKILL.md 正文
e2e-lifecycle-tombstone
E2E fixture skill (HATS-1147). Exists only so the retirement e2e can compose a
role whose skill declares lifecycle_hooks: — the channel deleted by ADR-0019
D8 — and assert that a real ai-hats self init refuses it by name. Not part of
the shipped library.
04 同仓库更多 Skills
tool-evaluation-protocol
Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML/LLM frameworks, testing approaches), or following up on a hype-driven recommendation.
systematic-debugging
4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.
skill-template
Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.
skill-optimization
Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.
silent-fallback-gate
PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.
retro-to-framework
Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.