メニュー
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Activate when starting new work to check for established patterns. Activate when ensuring consistency with team standards or when promoting successful memory patterns. Searches and applies best practices before implementation.
Activate when user wants to save knowledge, search past decisions, or manage persistent memories. Handles architecture patterns, implementation logic, issues/fixes, and past implementations. Uses local SQLite + FTS5 + vector embeddings for fast hybrid search. Supports write, search, update, archive, and list operations.
Activate when user explicitly requests the development workflow process, asks about workflow phases, or says "start work", "begin development", "follow the process". Activate when creating PRs or deploying to production. NOT for simple questions or minor fixes. Executes AUTONOMOUSLY - only pauses when human decision is genuinely required.
Activate when reviewing code, before committing, after committing, or before merging a PR. Activate when user asks to review, audit, check for security issues, or find regressions. Analyzes code for logic errors, regressions, edge cases, security issues, and test gaps. Fixes findings AUTOMATICALLY. Required at process skill quality gates.
Activate when user asks to commit, push changes, create a PR, open a pull request, or submit changes for review. Activate when process skill reaches commit or PR phase. Provides commit message formatting and PR structure. PRs default to dev branch, not main. Works with git-privacy skill.
Activate when asked to auto-review and merge a PR. Runs a closed-loop workflow: subagent Stage 3 review -> fix findings -> re-review -> post ICC-REVIEW receipt -> merge (optional via workflow.auto_merge).
| name | file-placement |
| description | Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces. |
Apply correct file placement rules for all output files.
File placement is enforced by hooks - violations will be blocked. This skill ensures you understand the rules so your work isn't rejected.
| File Type | Required Directory | Examples |
|---|---|---|
| Summaries | summaries/ | execution-summary.md, review-summary.md |
| Reports | summaries/ | analysis-report.md, audit-report.md |
| Stories | stories/ | STORY-001-feature.md |
| Bugs | bugs/ | BUG-001-issue.md |
| Memory | memory/ | memory/auth/oauth2.md |
| Documentation | docs/ | api-docs.md, architecture.md |
NEVER place these in the wrong location:
docs/ or project rootdocs/ or project rootmemory/Only these filenames may be ALL-CAPS:
All other files: Use lowercase-kebab-case
execution-summary.md (correct)EXECUTION-SUMMARY.md (blocked)The summary-file-enforcement.js hook will:
summaries/Ask yourself:
summaries/memory/<topic>/This skill provides guidance - you understand the rules. The hook provides enforcement - violations are blocked.
Together they ensure consistent file organization even when: