create-pr

Create consistent pull requests to be submitted to main via Github. Use when asked to commit a message, push or open a PR.

10 stars

byFilipeJesus

View on GitHub Installation ↓

Best use case

create-pr is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create consistent pull requests to be submitted to main via Github. Use when asked to commit a message, push or open a PR.

Teams using create-pr should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/create-pr/SKILL.md --create-dirs "https://raw.githubusercontent.com/FilipeJesus/lanes/main/.claude/skills/create-pr/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/create-pr/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How create-pr Compares

Feature / Agent	create-pr	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Create consistent pull requests to be submitted to main via Github. Use when asked to commit a message, push or open a PR.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Create Pull Request

You are an expert at creating pull requests for the Lanes project. Follow the contribution guidelines from CONTRIBUTING.md precisely.

## Prerequisites

Before creating a PR, ensure:
1. All tests pass: `npm run lint && npm test`
2. Documentation is updated if changes affect user-facing behavior
3. Tests are included for any new functionality
4. Branch follows naming convention:
   - `feat-` - New features
   - `fix-` - Bug fixes
   - `refactor-` - Code refactoring
   - `docs-` - Documentation changes
   - `test-` - Test additions

## Process

1. **Check current state**
   - Run `git status` to see current changes
   - Run `npm run lint && npm test` to verify everything passes
   - If tests fail, fix them before proceeding

2. **Check branch name**
   - Verify current branch follows the naming convention
   - If not, ask the user to provide the appropriate branch name

3. **Commit changes** (if not already committed)
   - This project enforces [Conventional Commits](https://www.conventionalcommits.org/) via commitlint (commit-msg hook)
   - Format: `type(scope): description`
   - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`
   - Examples: `feat: add tmux terminal backend`, `fix(sessions): prevent duplicate worktree creation`

4. **Push to remote**
   - Push the current branch to the fork/remote

5. **Create PR using gh CLI**
   - Base branch: `main`
   - Fill in the PR description with:
     - Clear description of changes
     - Related issues (if any)
     - Testing performed
     - Screenshots (if applicable)

6. **Verify PR creation**
   - Confirm the PR was created successfully
   - Provide the PR URL to the user

## PR Description Template

```markdown
## Summary
[Brief description of changes]

## Changes
- [List key changes]

## Related Issues
Closes #[issue_number] (if applicable)

## Testing
- [Describe testing performed]
- All tests pass: `npm run lint && npm test`

## Checklist
- [ ] Code follows project standards
- [ ] Tests are included and passing
- [ ] Documentation is updated (if applicable)
- [ ] No breaking changes without discussion
- [ ] Commit history is clean
```

## Important Notes

- Never push to `main` directly
- Always create a feature branch first
- Ensure CI checks pass before marking as ready for review
- Address review feedback promptly
```

---

Co-Authored-By: Claude <noreply@anthropic.com>

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.