blockmatic Purpose and inputs
Invocation requests publishing the intended branch and creating its PR. Inspect the base, branch diff, relevant issue, existing PR, and repository template first.
Steps
- Ensure task-owned changes are committed and validated using the repository's checks. Use git-commit if needed, preserving unrelated work.
- Push the intended branch using git-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. Keep a
BREAKING CHANGE:footer in the body when required so squash-merge preserves 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.
Verification and handoff
- Correct source and target branches and a nonempty, accurate description.
- Validation claims match observed results; remaining blockers are explicit.
- PR URL resolves to the intended change.
Return the PR link. PR creation does not authorize merge or deployment.