pr
Open a pull request for the current feature
How do I install this agent skill?
npx skills add https://github.com/remotion-dev/remotion --skill prIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides automated workflows for creating pull requests, including code formatting, building, and linting. It demonstrates a security-first approach by explicitly instructing the agent to use temporary files for pull request bodies to mitigate potential command injection vulnerabilities.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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:
- Write the PR body to a temporary Markdown file in the system temp directory (for example
/tmp/remotion-pr-body.md, or a unique file created under/tmp).- If the current work was started from, fixes, or is otherwise tied to a GitHub issue, include a closing keyword in the PR body such as
Closes #1234orCloses https://github.com/owner/repo/issues/1234. Preserve the issue number or URL from the user's original request if they provided one.
- If the current work was started from, fixes, or is otherwise tied to a GitHub issue, include a closing keyword in the PR body such as
- Create the PR with
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
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/remotion-dev/remotion/pr">View pr on skillZs</a>