Submit current work as a GitHub pull request, handling relevant uncommitted changes and reviewing prose before pushing. After creating the PR, run companion skills to generate changelog files, update the description, and return its URL.
Create and submit a GitHub PR from the current branch
Review the instructions the agent will receive before you install.
Submit 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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create changelog files for significant changes in a pull request, a proposed code change. Describe effects users will notice and organize entries by PR number and change type, such as features or fixes.
Review and improve code changes on the current branch using Pipecat conventions. Refine names and structure, add type hints and documentation, check example patterns, and make conservative performance improvements while preserving compatibility.
Review GitHub pull requests with specialized agents that check for clear bugs and violations of project instructions in CLAUDE.md. Validate bug findings before posting focused comments on the affected lines, with fix suggestions where appropriate.
Add or improve Google-style docstrings, the explanations embedded in Python code, for modules and classes. Document constructor arguments, public methods, configuration fields, and enum values while preserving existing documentation that already meets the project’s conventions.
Draft or update GitHub pull request descriptions using the actual changes and related context. Explain the problem, changed behavior, and review concerns in plain language, including breaking changes and explicit issue-closing references when applicable.
Review newly added comments, docstrings, and changelog entries so future readers can understand the current code. Revise development history, redundant explanations, and unclear shorthand while preserving constraints that the code cannot explain on its own.