Prompt file imported from binnicordova/jobync.com (.github/prompts/CREATE-PR.prompt.md). Copyright stays with the author.

Prompt for Pull Request Creation using GitHub CLI (gh)

Name: CREATE-PR
Author: binnicordova

This prompt is designed to automate the creation of high-quality Pull Requests (PRs) from the current feature branch to the main branch, ensuring all context, changes, and testing results are documented.

📋 PR Guidelines

Before creating the PR, the agent must gather specific information about the changes made in the current branch.

1. Change Analysis

# Get a summary of changes compared to main
git diff main...HEAD --stat
# Get the commit messages
git log main...HEAD --oneline

2. Information Gathering

The agent must identify:

Feature/Fix: What was the primary goal?
Breaking Changes: Are there any?
Testing: Have unit tests and coverage been verified? (Reference EXPO-TEST-SETUP.instructions.md)
Branding: Have assets been updated if necessary?

🚀 Execution Steps

1. Push Changes

Ensure the local branch is pushed to the remote.

git push origin $(git branch --show-current)

2. Generate PR Content

The PR title and body should follow a professional structure.

Title Pattern: prefix(scope): brief description Examples: feat(web): add eas build support for web, fix(ui): update AppBar spacing

Body Template:

## Summary
[Explain the 'why' and 'what' of the changes]

## Changes
- [Change 1]
- [Change 2]

## Testing Status
- [ ] Unit tests passing
- [ ] Coverage > 80%
- [ ] Verified on Web/iOS/Android

## Screenshots/Videos (if UI)
[Add links or placeholders]

3. Create PR command

gh pr create --base main --head $(git branch --show-current) --title "[Title]" --body "[Body]"

Success Criteria

✅ Clean Title: Follows conventional commits.
✅ Detailed Body: Explains logic and impact.
✅ Correct Branching: Target is always main.
✅ GitHub CLI: Command executes successfully and returns the PR URL.

Note: Ensure gh is authenticated before running this prompt.

# Prompt for Pull Request Creation using GitHub CLI (gh) This prompt is designed to automate the creation of high-quality Pull Requests (PRs) from the current feature branch to the `main` branch, ensuring all context, changes, and testing results are documented. ## 📋 PR Guidelines Before creating the PR, the agent must gather specific information about the changes made in the current branch. ### 1. Change Analysis ```bash # Get a summary of changes compared to main git diff main...HEAD --stat # Get the commit messages git log main...HEAD --oneline ``` ### 2. Information Gathering The agent must identify: - **Feature/Fix**: What was the primary goal? - **Breaking Changes**: Are there any? - **Testing**: Have unit tests and coverage been verified? (Reference `EXPO-TEST-SETUP.instructions.md`) - **Branding**: Have assets been updated if necessary? ## 🚀 Execution Steps ### 1. Push Changes Ensure the local branch is pushed to the remote. ```bash git push origin $(git branch --show-current) ``` ### 2. Generate PR Content The PR title and body should follow a professional structure. **Title Pattern:** `prefix(scope): brief description` *Examples: `feat(web): add eas build support for web`, `fix(ui): update AppBar spacing`* **Body Template:** ```markdown ## Summary [Explain the 'why' and 'what' of the changes] ## Changes - [Change 1] - [Change 2] ## Testing Status - [ ] Unit tests passing - [ ] Coverage > 80% - [ ] Verified on Web/iOS/Android ## Screenshots/Videos (if UI) [Add links or placeholders] ``` ### 3. Create PR command ```bash gh pr create --base main --head $(git branch --show-current) --title "[Title]" --body "[Body]" ``` ## Success Criteria - ✅ **Clean Title**: Follows conventional commits. - ✅ **Detailed Body**: Explains logic and impact. - ✅ **Correct Branching**: Target is always `main`. - ✅ **GitHub CLI**: Command executes successfully and returns the PR URL. --- **Note**: Ensure `gh` is authenticated before running this prompt.

{ "prompt": "# Prompt for Pull Request Creation using GitHub CLI (gh)\n\nThis prompt is designed to automate the creation of high-quality Pull Requests (PRs) from the current feature branch to the `main` branch, ensuring all context, changes, and testing results are documented.\n\n## 📋 PR Guidelines\n\nBefore creating the PR, the agent must gather specific information about the changes made in the current branch.\n\n### 1. Change Analysis\n```bash\n# Get a summary of changes compared to main\ngit diff main...HEAD --stat\n# Get the commit messages\ngit log main...HEAD --oneline\n```\n\n### 2. Information Gathering\nThe agent must identify:\n- **Feature/Fix**: What was the primary goal?\n- **Breaking Changes**: Are there any?\n- **Testing**: Have unit tests and coverage been verified? (Reference `EXPO-TEST-SETUP.instructions.md`)\n- **Branding**: Have assets been updated if necessary?\n\n## 🚀 Execution Steps\n\n### 1. Push Changes\nEnsure the local branch is pushed to the remote.\n```bash\ngit push origin $(git branch --show-current)\n```\n\n### 2. Generate PR Content\nThe PR title and body should follow a professional structure.\n\n**Title Pattern:** `prefix(scope): brief description`\n*Examples: `feat(web): add eas build support for web`, `fix(ui): update AppBar spacing`*\n\n**Body Template:**\n```markdown\n## Summary\n[Explain the 'why' and 'what' of the changes]\n\n## Changes\n- [Change 1]\n- [Change 2]\n\n## Testing Status\n- [ ] Unit tests passing\n- [ ] Coverage > 80%\n- [ ] Verified on Web/iOS/Android\n\n## Screenshots/Videos (if UI)\n[Add links or placeholders]\n```\n\n### 3. Create PR command\n```bash\ngh pr create --base main --head $(git branch --show-current) --title \"[Title]\" --body \"[Body]\"\n```\n\n## Success Criteria\n- ✅ **Clean Title**: Follows conventional commits.\n- ✅ **Detailed Body**: Explains logic and impact.\n- ✅ **Correct Branching**: Target is always `main`.\n- ✅ **GitHub CLI**: Command executes successfully and returns the PR URL.\n\n---\n**Note**: Ensure `gh` is authenticated before running this prompt.", "variables": [], "notes": "This prompt is designed to automate the creation of high-quality Pull Requests (PRs) from the current feature branch to the `main` branch, ensuring all context, changes, and testing results are documented.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/binnicordova/jobync.com", "path": ".github/prompts/CREATE-PR.prompt.md", "ref": "a610978f12c3f7c73cec363d8eb90c9548dde3ce", "url": "https://github.com/binnicordova/jobync.com/blob/a610978f12c3f7c73cec363d8eb90c9548dde3ce/.github/prompts/CREATE-PR.prompt.md", "key": "binnicordova/jobync.com/.github/prompts/CREATE-PR.prompt.md" } } }

CREATE-PR

About

Prompt for Pull Request Creation using GitHub CLI (gh)

📋 PR Guidelines

1. Change Analysis

2. Information Gathering

🚀 Execution Steps

1. Push Changes

2. Generate PR Content

3. Create PR command

Success Criteria

Use it

Manifest

Reviews