メニュー
This skill should be used when the user asks to "create a PR", "open a pull request", "submit for review", or wants to push and open a PR with an AI-generated summary and checklist.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ignite-ember/igni --skill prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
This skill should be used when the user asks to "resolve issues", "fix what CodeIndex flagged", "fix the issues in my branch", or otherwise wants the issues already detected by CodeIndex on their recent changes to be applied. Pulls issues from CodeIndex (not GitHub/GitLab APIs) and fixes them. After fixing, replies on the matching PR/MR review threads with the resolution narrative.
This skill should be used when the user asks to "explain", "how does X work", "what does X do", or wants a deep-dive explanation of code.
This skill should be used when the user asks to "commit", "save changes", "create a commit", or mentions git commit. Creates a well-formatted commit with conventional message.
| name | pr |
| description | This skill should be used when the user asks to "create a PR", "open a pull request", "submit for review", or wants to push and open a PR with an AI-generated summary and checklist. |
| category | operations |
| argument-hint | ["base-branch"] |
Create a pull request with an AI-generated summary and AI usage checklist.
Check for uncommitted changes. Run git status. If there are unstaged or staged changes that haven't been committed, suggest running /commit first. Do not proceed with uncommitted changes.
Determine the base branch. If $ARGUMENTS provides a branch name, use it. Otherwise, detect the default branch: try git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@', then fall back to main, then master. Verify the base branch exists.
Determine the current branch. Run git branch --show-current. If on the base branch, tell the user to create a feature branch first.
Check for existing PR. Run gh pr view --json number,state,url 2>/dev/null. If an open PR already exists for this branch, show its URL and ask if the user wants to update it or create a new one.
Get the full diff. Run git diff $BASE...HEAD to see all changes that will be in the PR.
Get the commit history. Run git log $BASE..HEAD --oneline to understand the logical progression of changes.
Read project guidelines. Check for ember.md, CONTRIBUTING.md, or PR template at .github/pull_request_template.md. If a template exists, follow its structure.
Write the PR title. Under 70 characters, imperative mood. Summarize the high-level intent, not the implementation details.
Write the PR body with these sections:
## Summary
<!-- 1-3 sentences: what changed and why -->
## Changes
<!-- Bullet list of logical changes, grouped by area -->
## AI Usage
- [ ] AI-generated code has been reviewed by a human
- [ ] Tests cover AI-generated logic
- [ ] No hallucinated imports or dependencies
- [ ] Security-sensitive code manually verified
<!-- Check all that apply: -->
- [ ] AI was used for implementation
- [ ] AI was used for test generation
- [ ] AI was used for code review
- [ ] AI was used for documentation
## Test Plan
<!-- How was this tested? What commands to run? -->
Check for gh CLI. Run which gh. If not installed:
Push the branch. Run git push -u origin HEAD.
Create the PR. Run:
gh pr create --title "<title>" --body "<body>" --base <base-branch>
Use a HEREDOC for the body to preserve formatting.
Show the result. Display the PR URL.
--draft flag.gh CLI: Degrade gracefully — output the PR content as markdown for manual creation.