소스 정보
- 저장소
- ROCm/rocprofiler-systems-skills
- 최근 소스 활동
- 2026년 2월 12일 13:28
- 감지된 SKILL.md 언어
- 영어
- 스타
- 4
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- git
- description
- Git workflow dispatcher - routes to specialized git skills for commits, PRs, and reviews
# Git Skills Dispatcher
**DO NOT use this skill directly.** Instead, use one of the specialized git skills below based on the user's request.
## Available Git Skills
### Commit Management
**`git/commit`** - Create meaningful git commits
- **When:** User wants to commit changes
- **Triggers:** "commit", "save changes", "create commit"
- **Location:** `~/.claude/skills/git/commit/SKILL.md`
### Pull Request Workflows
**`git/prepare-pull-request`** - Prepare and create pull requests
- **When:** User wants to create a PR
- **Triggers:** "create PR", "make pull request", "prepare PR"
- **Location:** `~/.claude/skills/git/prepare-pull-request/SKILL.md`
**`git/review-pull-request`** - Review pull requests with comprehensive checklist
- **When:** User wants to review a PR
- **Triggers:** "review PR", "check pull request"
- **Location:** `~/.claude/skills/git/review-pull-request/SKILL.md`
**`git/pull-request-status`** - Check PR status and CI results
- **When:** User wants to check PR status
- **Triggers:** "PR status", "check CI", "PR checks"
- **Location:** `~/.claude/skills/git/pull-request-status/SKILL.md`
### GitHub Operations
**`git/gh-client`** - GitHub CLI operations
- **When:** User needs GitHub-specific operations
- **Triggers:** "GitHub", "gh", "issues", "releases"
- **Location:** `~/.claude/skills/git/gh-client/SKILL.md`
## How to Use
When the user requests a git-related task:
1. **Identify the appropriate sub-skill** from the list above
2. **Load that specific skill** (if nested skills are supported)
3. **OR notify the user** that nested skills aren't currently loaded
## Fallback
If nested skills aren't recognized by Claude Code, you should inform the user that they need to:
- Use symlinks at the top level, OR
- Flatten the skill directory structure
## Example Routing
| User Request | Route To |
|--------------|----------|
| "commit my changes" | `git/commit` |
| "create a pull request" | `git/prepare-pull-request` |
| "review PR #123" | `git/review-pull-request` |
| "check PR status" | `git/pull-request-status` |
| "create GitHub issue" | `git/gh-client` |
GitHub에서 보기