메뉴
Locate and work with dwmkerr's repositories. Use when user mentions "my repos", "my repo X", "check my repo", or needs to find/access a specific repository.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and manage presentation decks. Two modes - Slidev markdown (default) and "conference" hand-built HTML. Use when user asks to "create slides", "make a presentation", "add slides to this project", "set up a slide deck", or mentions "slidev", "pitch deck", "conference talk", "conference deck", or "slides folder".
This skill should be used when the user asks to "create a skill", "write a skill", "build a skill", or wants to add new capabilities to Claude Code. Use when developing SKILL.md files, organizing skill content, or improving existing skills. Do NOT use for plugin development, hook creation, agent creation, or slash command creation — those have dedicated skills.
This skill should be used when the user says "solve problem", "solve this problem", or invokes /solve-problem. Applies a methodical, evidence-first approach to diagnosing a problem - understand intent, observe the problem first-hand, form multiple hypotheses, gather discriminating evidence to eliminate them, propose an evidenced solution, and verify the fix actually resolves the original symptom. Do NOT use for general how-to questions, explanations, or building new features.
This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.
Create a new GitHub project with standard configuration. Use when user asks to "create a project", "set up a new repo", "initialize a repository", or wants to start a new GitHub project.
This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", or mentions Claude Code hooks. Also suggest this skill when the user asks to "automatically do X" or "run X before/after Y" as these are good candidates for hooks.
| name | my-repos |
| description | Locate and work with dwmkerr's repositories. Use when user mentions "my repos", "my repo X", "check my repo", or needs to find/access a specific repository. |
Guide for locating and working with dwmkerr's repositories.
~/repos/
├── github/
│ ├── dwmkerr/ # Personal repos (github.com/dwmkerr)
│ │ ├── effective-shell/
│ │ ├── hacker-laws/
│ │ ├── claude-toolkit/
│ │ └── ...
│ └── mckinsey/ # McKinsey open source repos (github.com/mckinsey)
│ └── ...
Always check if the repo exists locally:
ls ~/repos/github/dwmkerr/<repo-name>
ls ~/repos/github/mckinsey/<repo-name>
When working with an existing local repo:
Record the current state before making changes:
cd ~/repos/github/dwmkerr/<repo>
ORIGINAL_BRANCH=$(git branch --show-current)
git stash --include-untracked
Fetch for reference if you need other branches:
git fetch origin
git checkout origin/main # or any branch for reference
Always return to original state when done:
git checkout "$ORIGINAL_BRANCH"
git stash pop
Check if it exists on GitHub:
gh repo view dwmkerr/<repo-name> --json name,url
If it exists remotely, clone it:
git clone https://github.com/dwmkerr/<repo-name> ~/repos/github/dwmkerr/<repo-name>
For McKinsey repos:
gh repo view mckinsey/<repo-name> --json name,url
git clone https://github.com/mckinsey/<repo-name> ~/repos/github/mckinsey/<repo-name>
dwmkerr~/repos/github/dwmkerr/~/repos/github/mckinsey/Some frequently accessed repositories:
effective-shell - Book and website for shell/terminal skillshacker-laws - Laws, theories, and patterns for developersclaude-toolkit - Claude Code plugins and skillsdotfiles - Personal configuration filesUser: "Check my repo effective-shell for the chapter on pipes"
ls ~/repos/github/dwmkerr/effective-shellgrep -r "pipes" ~/repos/github/dwmkerr/effective-shell/User: "What branches are in my repo X?"
cd ~/repos/github/dwmkerr/X && git branch -a