القائمة
Template, notes, and procedure when creating a Pull Request
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | create-pr |
| description | Template, notes, and procedure when creating a Pull Request |
gh pr createAI-agent → main<type>: <summary>
| type | usage |
|---|---|
feat | New feature |
fix | Bug fix |
refactor | Refactoring |
docs | Documentation change |
chore | Build/config change |
style | Formatting/style change |
feat: add neovim telescope config
fix: resolve fish greeting display bug
chore: update flake.lock
## Summary
<!-- What this PR does -->
## Changes
-
## Notes
<!-- Anything reviewers should know (optional) -->
gh pr create \
--base main \
--head AI-agent \
--title "<type>: <summary>" \
--body "$(cat <<'EOF'
## Summary
## Changes
-
## Notes
EOF
)"
gh pr list --base main --head AI-agent — if an open PR exists, do not create a new onegit log --oneline origin/main..HEAD before creating a PR--force-pushUse this skill whenever the user wants to merge the main branch into their current branch. Triggers include phrases like "merge main", "mainをマージ", "mainを取り込む", "mainに追従", "sync with main", "mainの変更を取り込みたい", or any request to bring changes from main into a feature/working branch. Always use this skill — do not improvise git commands without it.
Template and notes when creating or updating SKILL.md files under skills/
Perspectives and rules when conducting a code review
Rules for Git commits, pushes, and PR creation
When creating, editing, or debugging GitHub Actions workflow YAML files
Constraints when operating files in an Linux environment