.agents/skills/pr/SKILL.md
This skill is only for opening the initial pull request from finished local work.
If a PR already exists for the current branch, stop: do not format, commit, push, amend, or rebase unless the user explicitly asks for that Git action. Leave follow-up changes uncommitted by default.
Ensure we are not on the main branch, make a branch if necessary.
Check whether a PR already exists for the current branch with gh pr status or gh pr view. If it exists, report it and stop.
Run Oxfmt on the files or package directories affected by the current change. Pass their actual paths; do not assume that the repository root has a src directory. Include relevant root-level files, and do not format unrelated packages or the whole repository.
For example:
bunx oxfmt <changed-file-or-package-directory>... --write
If none of the changed files are supported by Oxfmt, skip this step. Inspect any formatter changes before committing.
Then run
bun run build
bun run stylecheck
to ensure we compile and CI linting/formatting passes.
Commit the changes once. The title of the PR must be according to the pr-name skill.
Push the changes to the remote branch once, using git push -u origin HEAD.
Never force push. Do not use git push --force, git push -f, or git push --force-with-lease. If a normal push is rejected, stop and report the rejection to the user instead of rewriting remote history.
Use the gh CLI to create a pull request and use the same format as above for the title.
When creating the PR, do not pass the PR body inline through a shell command (for example, avoid --body "..." or heredocs in bash). Instead:
/tmp/remotion-pr-body.md, or a unique file created under /tmp).
Closes #1234 or Closes https://github.com/owner/repo/issues/1234. Preserve the issue number or URL from the user's original request if they provided one.gh pr create --title "<title>" --body-file <path-to-temp-md-file>.Example:
gh pr create --title '`@remotion/package`: Add feature' --body-file /tmp/remotion-pr-body.md