Custom Submit Pr

Submit Pull Request

This skill pushes the current branch and creates a GitHub pull request using gh, with a description generated by the custom-pr-summary skill and polished by the custom-writing-style-guide skill, assigned to Chris.

Process

Step 0: Parse Arguments

Check ARGUMENTS for:

• The word draft (case-insensitive) → set DRAFT=true, otherwise DRAFT=false
• doc-path: key → if present, store its value as DOC_PATH to pass to custom-pr-summary

Step 1: Validate Branch

git branch --show-current

If on main or master, stop and inform Chris this doesn't make sense for the main branch.

Step 2: Check for Unpushed Changes

git status

If there are uncommitted changes, stop and inform Chris. Do not commit automatically.

Step 3: Push Branch

Check if the branch has a remote tracking branch. If not, push with -u:

git push -u origin 

If it already tracks a remote, just push:

git push

Step 4: Generate PR Description

Invoke the custom-pr-summary skill to generate the PR description. If DOC_PATH is set, pass it as doc-path: . Otherwise invoke with no arguments (discovery runs automatically).

Take the generated summary — only the "Summary" section content, no "Key Review Areas" or "Files Changed" sections.

Step 5: Apply Writing Style Guide

Write the summary text to a temporary markdown file:

TMPFILE=$(mktemp /tmp/pr-summary-XXXXXX.md)
cat > "$TMPFILE" 
EOF

Invoke the custom-writing-style-guide skill with the temp file path as the argument, using batch mode (no interactive review). This rewrites the prose to match Chris's voice.

Read back the rewritten content from the temp file, then delete it:

cat "$TMPFILE"
rm "$TMPFILE"

Use the rewritten content as the PR body.

Step 6: Determine PR Title

Derive a short PR title (under 70 characters) from the feature doc heading or the summary. Use imperative mood (e.g., "Add tutorial system foundation", not "Added" or "Adds"). Apply the writing style guide voice to the title too — keep it punchy and direct.

Step 7: Create Pull Request

If DRAFT=false:

gh pr create --assignee assertchris --reviewer assertchris --title "" --body "$(cat 

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

If DRAFT=true, add the --draft flag:

gh pr create --draft --assignee assertchris --reviewer assertchris --title "" --body "$(cat 

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Step 8: Report

Output the PR URL so Chris can see it. If it was created as a draft, say so explicitly.

Don'ts

1. DON'T include checkboxes, test plans, or checklists in the PR body
2. DON'T include "Files Changed" or "Key Review Areas" sections
3. DON'T commit uncommitted changes — only push and create the PR
4. DON'T assign or add as reviewer anyone other than assertchris
5. DON'T create a draft PR unless Chris explicitly asked for one
6. DON'T force push
7. DON'T leave the temp file behind if an error occurs — always clean it up

Success Criteria

• Branch is pushed to remote
• PR description has been styled through the writing style guide
• PR is created via gh with a concise, voice-consistent summary
• PR is assigned to assertchris
• PR has assertchris as a reviewer
• PR is a draft if and only if Chris asked for a draft
• PR URL is displayed

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: assertchris
• Source: assertchris/claude-skills
• License: MIT

Install and usage instructions live in the source repository linked above.