Create and submit a GitHub PR from the current branch
63
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/pr-submit/SKILL.mdSubmit the current changes as a GitHub pull request.
Check the current state of the repository:
git status to see staged, unstaged, and untracked changesgit diff to see current changesgit log --oneline -10 to see recent commitsIf there are uncommitted changes relevant to the PR:
alice/, fix/, feat/)Run /prose-review branch and fix anything it flags. Do this before pushing,
while corrections are still cheap.
Push the branch and create the PR:
-u flag to set upstream trackinggh pr createAfter the PR is created:
/changelog <pr_number> to generate changelog files, then commit and push them/pr-description <pr_number> to update the PR descriptionBoth skills review their own prose — no separate pass is needed here.
Return the PR URL to the user.
Commit messages are prose too — /prose-review reads diffs and so won't see them.
Read the messages in git log main..HEAD against the same standard before pushing.
6659b78
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.