ワンクリックで
init
Analyze project structure and update AGENTS.md with detected tech stack, commands, and configurations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Analyze project structure and update AGENTS.md with detected tech stack, commands, and configurations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Save session context to agent configuration files or create full checkpoint files. Supports three modes: session history (default), full checkpoint (--full), and skill analysis (--full --analyze) for extracting reusable patterns.
PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".
PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "記録して", "設計どうなってる", "record this". Do NOT wait for user to ask - record important decisions immediately.
PROACTIVELY consult Gemini CLI for research, large codebase comprehension, and multimodal data processing. Gemini excels at: massive context windows (1M tokens), Google Search grounding, video/audio/PDF analysis, and repository-wide understanding. Use for pre-implementation research, documentation analysis, and multimodal tasks. Explicit triggers: "research", "investigate", "analyze video/audio/PDF", "understand codebase".
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
Research a library and create comprehensive documentation in .claude/docs/libraries/.
| name | init |
| description | Analyze project structure and update AGENTS.md with detected tech stack, commands, and configurations. |
| disable-model-invocation | true |
Analyze this project and update only the project-specific sections of AGENTS.md.
Find these files to identify the tech stack:
package.json → Node.js/TypeScript projectpyproject.toml / setup.py / requirements.txt → Python projectCargo.toml → Rust projectgo.mod → Go projectMakefile / Dockerfile → Build/deploy config.github/workflows/ → CI/CD configAlso detect:
Use AskUserQuestion tool to ask:
Use Edit tool to update only the top section (up to first ---) with this format:
# Project Overview
{User's answer}
## Language Settings
- **Thinking/Reasoning**: English
- **Code**: {Based on analysis - English or Korean}
- **User Communication**: Korean
## Tech Stack
- **Language**: {Detected language}
- **Package Manager**: {Detected tools}
- **Dev Tools**: {Detected tools}
- **Main Libraries**: {Detected libraries}
Update the ## Common Commands section with detected commands:
## Common Commands
```bash
# Detected commands (example)
{npm run dev / poe test / make build etc.}
### 5. Check Unnecessary Rules
Check rules in `.claude/rules/` and suggest removing unnecessary ones:
- Non-Python project → `dev-environment.md` (uv/ruff/ty) may not be needed
- No-test project → `testing.md` may not be needed
### 6. Report Completion
Report to user (in Korean):
- Detected tech stack
- Updated sections
- Recommended rules to remove (if any)