메뉴
Reads from an existing issue, interprets expected outcomes, plans before making changes
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate conventional commit message from staged or unstaged changes
Checks projects and packages for CVEs using Socket.dev CLI and native audit commands. Use when installing or auditing dependencies for vulnerabilities, evaluating a package before install, or scanning a project's dependency tree.
Audit the current project's memory store (`~/.claude/projects/<encoded-cwd>/memory/`) and prune memories that no longer match the project state — dead file/function/flag references, past-dated project memories, orphaned index entries, and duplicates. Suggests candidates with rationale and requires per-item confirmation before deleting; does not edit memory bodies. Use when the user says "prune memory", "clean up memory", "audit memory", "memory is stale", "remove old memories", or invokes /prune-memory.
Symlink every skill in this repo into one or more agent skills directories (defaults to ~/.claude/skills/ and ~/.agents/skills/) so the skills become globally discoverable. Use when the user says "install these skills", "make these skills global", "symlink skills to ~/.claude", "symlink skills to ~/.agents", "register the skills", or wants to update the global skill set after editing skills here.
Build, validate, and exercise the agent-skills registry. Use when asked to run agent-skills, install its deps, lint or test it, run its bats suites, exercise a Claude Code hook, regenerate the index files, or symlink the skills out to ~/.claude / ~/.agents / ~/.cursor / ~/.opencode.
Concise, technically-precise response style with kawaii flourishes (emojis, emoticons, otaku suffixes). Use when the user wants playful agent output while keeping technical accuracy and brevity.
| name | issue-plan-commit |
| description | Reads from an existing issue, interprets expected outcomes, plans before making changes |
Read the mentioned issue and tell me your understanding of the expected behaviour. We will discuss this until I agree your understanding is correct. Next, plan on tackling each problem one by one. Ask questions if it is unclear. Do NOT implement until I approve. Each solution should have a test. Commit after it passes. Next, run /simplify or /review on the committed changes.
