بنقرة واحدة
failure-postmortem
Structured logging and analysis of execution failures to prevent recurrence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Structured logging and analysis of execution failures to prevent recurrence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
A QA gate that validates potentially destructive or irreversible actions before execution.
Detect and prevent state-visibility violations across execution contexts within a single transaction.
Convert mixed terminal output and instructions into safe, paste-ready command blocks.
Prepares isolated sub-workspaces for parallel agent execution. Copies context and generates specific mission instructions for "Worker" agents.
Detects when the agent is stuck in a reasoning loop or unproductive state by analyzing tool usage and sentiment patterns.
Generates a 'Red Team' critique of recent code or plans to identify weak assumptions and edge cases.
| name | Failure Postmortem |
| description | Structured logging and analysis of execution failures to prevent recurrence. |
| version | 1.0.0 |
| author | Antigravity Skills Library |
| created | "2026-01-16T00:00:00.000Z" |
| leverage_score | 5/5 |
Systematically captures failure data. When a tool fails or a plan is abandoned, this skill logs the event to a persistent registry (POSTMORTEMS.md), forcing an synchronous analysis of why it happened (Root Cause) and how to prevent it (Preventive Rule).
log failurepostmortemwhy did this failrecord error| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
--Command | string | Yes | - | The command or action that failed |
--Error | string | Yes | - | The error message or exception trace |
--Context | string | No | General | What was the agent trying to do? |
Appends to .gemini/antigravity/.forensics/POSTMORTEMS.md:
## [2026-01-16 10:00:00] Failure Analysis
**Context:** Deployment
**Command:** `npm build`
**Error:** `Heap out of memory`
### 🕵️ Analysis
1. **Root Cause:** Node processes default to 512MB RAM.
2. **Preventive Rule:** Always set NODE_OPTIONS="--max-old-space-size=4096" for builds.
.forensics directory exists (auto-created).| Condition | Action |
|---|---|
| Disk Full | Fail gracefully (stdout only) |
See scripts/log_failure.ps1.
log_failure.ps1.