Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Invocation requests publishing the intended branch and creating its PR. Follow git publish. The description is part of this playbook; do not use a separate generate-description step.
- Ensure task-owned changes are committed and validated. Use commit if needed. If this playbook must create a branch first,
git fetch originthengit switch -c <name> --no-track origin/main— never skip fetch, never a stale localmain. - Push the intended branch using push.
- Write a standalone description: problem, resulting behavior, verification evidence, and material limitations. Follow the repository template; never create an empty description. Use a conventional PR title when the repository requires it.
- Reuse an existing PR for this branch rather than duplicating it. Use known applicable labels and requested reviewers; do not invent assignments.
- With a CLI, write multiline text to a temporary file and pass the body-file option. Verify the resulting title, base, and description. Return the PR link. PR creation does not authorize merge or deployment.
