Borrowing it
Nothing to install: this file belongs to FilipeJesus/lanes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FilipeJesus/lanes/main/.claude/skills/create-pr/SKILL.mdgit clone --depth 1 https://github.com/FilipeJesus/lanesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/filipejesus/lanes/create-pr)<a href="https://agentmods.dev/skills/filipejesus/lanes/create-pr"><img src="https://agentmods.dev/badge/skills/filipejesus/lanes/create-pr.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00624 |
| Opus 5 | $0.00015 | $0.00312 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
create-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
- All tests pass:
npm run lint && npm test - Documentation is updated if changes affect user-facing behavior
- Tests are included for any new functionality
- Branch follows naming convention:
feat-- New featuresfix-- Bug fixesrefactor-- Code refactoringdocs-- Documentation changestest-- Test additions
Process
-
Check current state
- Run
git statusto see current changes - Run
npm run lint && npm testto verify everything passes - If tests fail, fix them before proceeding
- Run
-
Check branch name
- Verify current branch follows the naming convention
- If not, ask the user to provide the appropriate branch name
-
Commit changes (if not already committed)
- This project enforces Conventional Commits 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
-
Push to remote
- Push the current branch to the fork/remote
-
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)
- Base branch:
-
Verify PR creation
- Confirm the PR was created successfully
- Provide the PR URL to the user
PR Description Template
## 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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 90 lines · 29 tokens per session scan A d01be80bd732
create-pr is a skill published in the GitHub repository FilipeJesus/lanes (11 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 624 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.