菜单
Agent session self-analysis workflow. Use at the end of a session or after user feedback to identify process failures, perform 5 Whys, and record durable learnings without duplicates. Trigger when: /self-analysis, self analysis, session retrospective, session learnings.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | session-self-analysis |
| description | Agent session self-analysis workflow. Use at the end of a session or after user feedback to identify process failures, perform 5 Whys, and record durable learnings without duplicates. Trigger when: /self-analysis, self analysis, session retrospective, session learnings. |
Analyze the current agent session and record durable lessons when needed.
.claude/memory/, a project session-learnings
file (if one exists), or a relevant .agent/skills/*/SKILL.md after
deduplication.Look for:
If no friction occurred, say so briefly and stop.
Use:
For the most important issue, ask why until the root cause is specific and actionable. Three to five steps are enough.
Good rule format:
[Trigger/context] -> [Expected behavior]
Rules must be concrete and testable. Avoid vague rules like "be more careful".
Search:
ls .claude/memory
rg -n "keyword|concept" .claude/memory .agent/skills
Destination:
| Type | Destination |
|---|---|
| process/workflow feedback | .claude/memory/feedback_*.md |
| code-level gotcha | project session-learnings file (if maintained) |
| domain-specific rule | relevant .agent/skills/*/SKILL.md |
If an existing file covers the concept, update it rather than creating a duplicate.
---
name: short-rule-name
description: One-line description
type: feedback
---
Rule statement.
**Why:** Incident that caused this rule.
**How to apply:** Trigger and concrete behavior.
After creating a memory file, add a one-line pointer to
.claude/memory/MEMORY.md (or the equivalent index in your project).
AGENTS.md / CLAUDE.md..claude/memory/ is the repo SSOT shared across
Claude / Codex / Copilot sessions. Per-machine user memory
(~/.claude/projects/.../memory/ for Claude Code) is invisible to other
agents — only sync rules worth sharing.Shared multi-agent presence and claim protocol. Use before any coding agent starts work in this repo, when coordinating Claude/Codex/Gemini sessions, or when checking who is already working on the repository. Triggers: agent session start, check agent presence, agent coordination, who's working on repo.
Claude Code adapter for the shared agent-presence protocol (for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`, for Gemini CLI use `.agent/skills/dispatch-watcher-gemini/SKILL.md`). Use on Claude session start to run pre-flight, claim Slack-dispatched issues (@claude #N), and emit lifecycle events. Triggers: Claude session start, /dispatch, /agent-presence, message addressed to @claude in the dispatch channel.
Gemini CLI adapter for the shared agent-presence protocol (for Claude Code use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`). Use on Gemini session start to run pre-flight, claim Slack-dispatched issues (@gemini #N), and emit lifecycle events. Triggers: Gemini session start, /dispatch, /agent-presence, message addressed to @gemini in the dispatch channel.
Optional agent dispatch watcher — Phase 1 walking skeleton, Codex-flavored. Use on agent session start when a Slack-style dispatch channel assigns GitHub issues to a model handle such as @codex. For Claude use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Gemini use `.agent/skills/dispatch-watcher-gemini/SKILL.md`, for the full multi-agent contract see `.agent/skills/agent-presence/SKILL.md`.
PR merge supervisor workflow. Use to merge a GitHub PR safely — resolve review threads correctly, check CI, run an optional repo supervisor, and do post-merge cleanup. Trigger when: /merge, merge PR, complete a PR, finalize a PR.
Use when generating operational reports, release notes, demo readiness checks, stakeholder updates, infrastructure cost/expiry checks, or bilingual changelogs. Triggers: /release-notes, /investor-report, /demo-check, /cost-check, changelog, release notes, stakeholder report, monthly metrics, demo readiness, before demo, infrastructure costs, cost monitoring, certificate expiry.