Aftermath

Post-failure recovery when something already broke: test suite went green to red, same error repeats after a fix, build or dependency resolution fails, a test is flaky, a merge conflicts, a destructive command is blocked, a forward edit is frozen, user says "you broke it", or the fix touched files outside scope. Stop, revert cheap damage, diagnose honestly, return to last-known-good. Supports lite/full/ultra, opt-in checkpoint autoRevert. Use ONLY for recovery after failure, not for planning new work.

14 starsTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add moah0911/aftermath --skill aftermath

Manual install

git clone --depth 1 https://github.com/moah0911/aftermath.git /tmp/aftermath
mkdir -p ~/.claude/skills
cp -r /tmp/aftermath/. ~/.claude/skills/aftermath

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Aftermath — using the recovery agent

You are operating the Aftermath recovery skill. Most skills teach how to build; this one fires **after something already broke**. Invoke it when any of these hold: a test suite went green to red, the same error recurred after a fix, a destructive command was blocked, a forward edit was frozen, the user corrected you, or the fix touched files outside scope.

## The ladder

Stop at the first rung that holds, before your next edit:

1. Uncommitted / one file / cheap to undo? → Revert now. Do not patch forward.
2. Last-known-good exists? → Diff it, isolate one change, revert just that.
3. 2nd+ failed attempt at the same fix? → State exact error, state theory, ask.
4. Next action irreversible? → Confirm state explicitly. Never assume.
5. Filling a gap with a guess? → Say so out loud. Never continue silently.
6. User just corrected you? → Do not defend. Find the diff. Fix only that.

Honesty: never hide a break. Never silently revert. Never invent an unverified root cause.

## Intensity and commands

- Levels: `lite` (suggest) · `full` (default: stop, diagnose, ask) · `ultra` (guards + opt-in checkpoint autoRevert) · `off`. Switch: `/aftermath [lite|full|ultra|off]`.

Read the full skill on GitHub

Details

Skill name: aftermath
Repository: moah0911/aftermath
License: MIT
Repo updated: 28 October 2026

FAQ

What does the Aftermath skill do?

How do I install the Aftermath skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add moah0911/aftermath --skill aftermath. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Aftermath popular?

It lives in moah0911/aftermath, which has 14 GitHub stars and 0 forks.

Related skills

Does It Work

TsakunovR/does-it-work

Проверка, что продукт реально работает, и защита его качества автотестами. Аудит работающего (в т.ч. навайбкоженного) приложения: найти баги, оценить готовность к проду, выдать баг-репорт с severity. Генерация тестовых фреймворков: API-тесты на Python (pytest + httpx + Pydantic + Allure) и Java (JUnit 5 + REST Assured), WEB/UI-тесты (Playwright, Selenium, Selenide, Page Object); конвертация OpenAPI/Postman/curl/HAR в тесты, негативные кейсы, контракты. Также стабилизация флакающих тестов и ревью качества тестов. Triggers: "проверь мой продукт/приложение", "найди баги", "навайбкодил", "можно ли

Testing & QA

QA Test Case Generation

saleem-daqa/qa-test-case-generation

Use when generating manual QA test cases from requirements, BRDs, user stories, acceptance criteria, spreadsheets, live mockup/prototype URLs, uploaded mockups, screenshots, wireframes, or existing test case templates; especially when coverage, deduplication, traceability, validations, permissions, workflows, or edge cases matter.

Testing & QA

Red Green Mode

hidevinliu/red-green-mode

Autonomous test-fix loop: run an objective verifier (tests, type-check, lint, CI), fix what is red, re-run, and finish only when the verifier exit code is all green. Use when the user wants work driven to green without supervision, including long-run or parallel runs (红绿灯模式 / 跑到全绿 / 把 CI 修到全绿). Not for subjective work with no verifier or one-shot edits; use test-driven-development to write tests and systematic-debugging to root-cause one bug.

Testing & QA

Laravel Nova to Filament

bkuhl/laravel-nova-to-filament-skill

Perform a complete, production-quality migration from Laravel Nova to Filament PHP v5. Covers field mapping, resources, actions, filters, lenses, metrics, dashboards, authorization, navigation, and testing with idiomatic Filament v5 patterns.

Testing & QA

Serial Protocol Assistant

10walnut/serial-protocol-tester-skill

Convert vendor serial communication specifications into validated, single-language serial_protocol.v1 JSON that drives a functional test console. Use to move quickly from protocol documents to host/device simulation, define variable formulas and multi-response streams, decode frames and checksums, or isolate host, device, script, and serial-link faults.

Testing & QA

Ic Testing Notes

wuyu25394-alt/sziit-speedcury-st2500-ate-skill

集成电路测试（ATE）知识库与实操手册，基于加速科技 ST2516/ST2500 测试平台与六个实训案例（CD4511 数字译码器、HK24C02 存储、LM358 运放、TPS73625 电源管理、HK32F031F4P6 MCU、ADC0832 数模混合），另含 74HC138、74HC595 扩展案例（3-8 译码器 / 8 位移位寄存器 + TMU 时序 + 虚拟 ATE）。当问题涉及 SMU/DPS/PPMU/BPMU/RVS/TMU/AWG/DGT/CBIT 等测试资源、开短路(OS)/漏电流(IIL/IIH)/VOH/VOL/IDD 等直流参数测试、Pattern 与 Timing 及 PinLevel 功能测试、FVMV/FVMI/FIMV/FIMI/FNMV 测量模式、ATE 工程文件（.job/.tmf/.sig/.grp/.res/.tim/.pat/Test.cpp）、或上述六款芯片的测试开发、限值设定与排错时使用。也适用于集成电路测试课程的复习、答疑、作业与实训。

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.