메뉴
Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, and writes a post-mortem for review. Use after an incident or outage.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Systematic performance profiling and optimization with a mandatory baseline-first gate — measure before changing, re-measure after. Use when something is slow or you need to hit a latency/throughput target.
Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, writes the post-mortem file and commits it. Use after an incident or outage.
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.
Thorough, research-grounded code review of a change, PR, or MR — multi-lens (correctness, security, simplification, tests), severity-ranked with impact + fix, configurable depth, optional PR comments. Use when asked to review code, "do a code review", "review this PR/MR", "review my changes/diff/branch", or audit a changeset before merge.
Use when the user asks to research, investigate, analyze, find out, explore, examine, audit, or evaluate something — structured multi-source research with consulting, library-doc search, web search, and guided output delivery.
Multi-agent code review AND remediation — dispatches correctness, security, and simplification reviewers in parallel, consolidates findings, then fixes criticals/highs. Use when reviewing a diff or PR before shipping.
| name | autopsy |
| description | Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, and writes a post-mortem for review. Use after an incident or outage. |
Read ../../references/codex-adapter.md, then read ../../source-skills/autopsy/SKILL.md and follow the source skill through that Codex adapter. Keep the source skill's gates, safety checks, and completion criteria.
Writing the approved post-mortem is in scope; committing it is a separate durable side effect. Stage only that task-owned artifact and commit only after explicit authorization.
