Skip to main content

radius-create-pr

Automates GitHub pull request creation from the current branch

소스 정보

저장소
radius-project/radius
최근 소스 활동
2026년 10월 21일 19:27
감지된 SKILL.md 언어
영어
스타
1,670
포크
140

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
radius-create-pr
description
Automates GitHub pull request creation from the current branch
disable-model-invocation
true
# Create GitHub Pull Request Create a pull request from the current branch following the steps below. ## Determining the Default Branch When working with forks, the default branch must come from the correct remote: - If `upstream` exists in `git remote -v`: run `git remote show upstream` and parse the output to find the `HEAD branch` - Otherwise: run `git remote show origin` and parse the output to find the `HEAD branch` > [!TIP] > On Linux or macOS for precise output parsing, consider using: `git remote show <your-remote-name> | grep 'HEAD branch'` > On Windows with PowerShell, you can use: `git remote show <your-remote-name> | Select-String 'HEAD branch'` ## Steps ### Step 1: Validate Branch State Stop and inform the user if any of these conditions exist: - Current branch has no remote tracking branch (`git rev-parse --abbrev-ref --symbolic-full-name "@{u}"`) - Uncommitted changes exist (`git status --porcelain`) - Unpushed commits exist (`git rev-list --count "@{u}..HEAD"` returns > 0) ### Step 2: Load PR Template Check for a PR template at these locations (in order): - `.github/PULL_REQUEST_TEMPLATE.md` - `.github/pull_request_template.md` - `docs/PULL_REQUEST_TEMPLATE.md` - `PULL_REQUEST_TEMPLATE.md` Use the first template found to structure the PR description. ### Step 3: Generate PR Content Analyze the changes using `git diff` and `git log` against the default branch. **PR Title Requirements:** - Maximum 80 characters - Use `<type>[optional scope][!]: <description>` with a lowercase type - Read the [PR title guide](../../../docs/contributing/contributing-pull-requests/README.md#3-use-a-conventional-commit-pull-request-title) and use its allowed types - Use noun phrases in the description, for example `feat(api): authentication improvements` **PR Description:** - Follow the PR template structure if one exists - Preserve checkboxes from the template (do not convert to bullets) - If no template: summarize changes, list modified files, include relevant commit context ### Step 4: Create the Pull Request Create the PR using the GitHub MCP tool, falling back to `gh pr create` if unavailable. - **head**: current branch - **base**: default branch (from Step 1) ### Step 5: Report Result Display the PR URL: ```text ✅ Pull request created successfully! 🔗 URL: [PR_URL] ``` ## Error Handling Stop immediately on any failure with a clear error message. Common errors: - Branch not pushed to remote - Uncommitted or unpushed changes - PR already exists for this branch - Insufficient GitHub permissions
GitHub에서 보기