Firewood Review
ava-labs/firewood
A skill your agent uses when reviewing ava-labs/firewood code changes — pull request or local workspace.
Create or update a PR from current branch to main, watch CI, and address feedback
Install Create PR
$ npx skills add dojoengine/dojo --skill create-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dojoengine/dojo create-pr --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-pr .claude/skills/create-pr && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .claude/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-prType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dojoengine/dojo --skill create-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dojoengine/dojo create-pr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-pr .agents/skills/create-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .agents/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dojoengine/dojo --skill create-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dojoengine/dojo create-pr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-pr .cursor/skills/create-pr && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .cursor/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dojoengine/dojo.git --path .agents/skills/create-pr--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dojoengine/dojo --skill create-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dojoengine/dojo create-pr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-pr .gemini/skills/create-pr && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .gemini/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dojoengine/dojo create-prInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dojoengine/dojo --skill create-pr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-pr .github/skills/create-pr && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .github/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dojoengine/dojo --skill create-pr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dojoengine/dojo create-pr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-pr .opencode/skills/create-pr && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-pr" agent skill from https://github.com/dojoengine/dojo/tree/main/.agents/skills/create-pr into .opencode/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
create-pr- GitHub stars
- 478
- Token cost
- ~1.1k tokens
- SKILL.md length
- 613 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or update a PR from current branch to main, watch CI, and address feedback
- Works in 4 steps: Review the code → Create/Update PR → Monitor CI and Address Issues → …
- Tasks that involve Pull requests
- SKILL.md covers Phase 1: Review the code, Phase 2: Create/Update PR, Phase 3: Monitor CI and… and Phase 4: Merge and Cleanup, plus 1 more section
- Runs Shell scripts from its folder; calls git and gh; needs GH_TOKEN and GITHUB_TOKEN
What it does
Create PR is an agent skill from dojoengine/dojo. Create or update a PR from current branch to main, watch CI, and address feedback
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/poll-pr.sh`, `scripts/pr-body-update.sh` and `scripts/triage-pr.sh`).
It sits in Development, covering Pull requests. It works with Rust and Git. The repository describes itself as: Dojo is a toolchain for building provable games and applications. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/create-pr”
Requirements
- A Bash shell
- A credential in GITHUB_TOKEN
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 19c258a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GH_TOKENGITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Create PR loads about 1.1k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 613 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from dojoengine/dojo at commit 19c258a, republished under its Apache-2.0 licence (© dojoengine). 613 words, ~1,059 tokens.
Download SKILL.mdSave it as
.claude/skills/create-pr/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- create-pr
- description
- Create or update a PR from current branch to main, watch CI, and address feedback
The user likes the state of the code.
There are $git status --porcelain | wc -l | tr -d ' ' uncommitted changes.
The current branch is $git branch --show-current.
The target branch is origin/main.
$git rev-parse --abbrev-ref @{upstream} 2>/dev/null && echo "Upstream branch exists." || echo "There is no upstream branch yet."
Existing PR: $gh pr view --json number,title,url --jq '"#\(.number): \(.title) - \(.url)"' 2>/dev/null || echo "None"
The user requested a PR.
Follow these exact steps:
Phase 1: Review the code
- Review test coverage
- Check for silent failures
- Verify code comments are accurate
- Review any new types
- General code review
Phase 2: Create/Update PR
- Run
git diffto review uncommitted changes - Commit them. Follow any instructions the user gave you about writing commit messages.
- Push to origin.
- Use
git diff origin/main...to review the full PR diff - Check if a PR already exists for this branch:
- If PR exists:
- Draft/update the description in a temp file (e.g.
/tmp/pr-body.txt). - Update the PR body using the non-deprecated script:
./.agents/skills/create-pr/scripts/pr-body-update.sh --file /tmp/pr-body.txt
- Re-fetch the body with
gh pr view --json body --jq .bodyto confirm it changed.
- Draft/update the description in a temp file (e.g.
- If no PR exists: Use
gh pr create --base mainto create a new PR. Keep the title under 80 characters and the description under five sentences.
The PR description should summarize ALL commits in the PR, not just the latest changes.
Phase 3: Monitor CI and Address Issues
Note: Keep commands CI-safe and avoid interactive gh prompts. Ensure GH_TOKEN or GITHUB_TOKEN is set in CI.
- Watch CI status and feedback using the polling script (instead of running
ghin a loop):
- Run
./.agents/skills/create-pr/scripts/poll-pr.sh --triage-on-change --exit-when-green(polls every 30s for 10 mins). - If checks fail, use
gh pr checksorgh run listto find the failing run id, then:- Fetch the failed check logs using
gh run view <run-id> --log-failed - Analyze the failure and fix the issue
- Commit and push the fix
- Continue polling until all checks pass
- Fetch the failed check logs using
- Check for merge conflicts:
- Run
git fetch origin main && git merge origin/main - If conflicts exist, resolve them sensibly
- Commit the merge resolution and push
- Use the polling script output to notice new reviews and comments (avoid direct polling via
gh):
- If you need a full snapshot, run
./.agents/skills/create-pr/scripts/triage-pr.shonce. - If you need full context after the script reports a new item, fetch details once with
gh pr view --commentsorgh api .... - Address feedback:
- For bot reviews, read the review body and any inline comments carefully
- Address comments that are clearly actionable (bug fixes, typos, simple improvements)
- Skip comments that require design decisions or user input
- For addressed feedback, commit fixes with a message referencing the review/comment
Show full SKILL.md (166 more words)Show less
Phase 4: Merge and Cleanup
Once CI passes and the PR is approved, ask the user if they want to merge the PR.
If the user confirms, merge the PR:
- Use
gh pr merge --squash --delete-branchto squash-merge and delete the remote branch
- Use
After successful merge, check if we're in a git worktree:
- Run:
[ "$(git rev-parse --git-common-dir)" != "$(git rev-parse --git-dir)" ] - If in a worktree: Use the ask user question tool (
request_user_input) to ask if they want to clean up the worktree. If yes, runwt remove --yes --forceto remove the worktree and local branch, then switch back to the main worktree. - If not in a worktree: Just switch back to main with
git checkout main && git pull
- Run:
Completion
Report the final PR status to the user, including:
- PR URL
- CI status (passed/merged)
- Any unresolved review comments that need user attention
- Cleanup status (worktree removed or branch switched)
If any step fails in a way you cannot resolve, ask the user for help.
© dojoengine, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in .agents/skills/create-pr of dojoengine/dojo.
- SKILL.md
- scripts/poll-pr.sh
- scripts/pr-body-update.sh
- scripts/triage-pr.sh
Open the folder on GitHubat commit 19c258a
Compare with similar skills
Create PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create PR this skilldojoengine/dojo | 478 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Firewood Reviewava-labs/firewood | 153 | — | ~2.1k | Automated safety check: Notes | Custom licence | |
| Mz PR ReviewMaterializeInc/materialize | 6.4k | — | ~1.6k | Automated safety check: Notes | Custom licence | |
| PRboundless-xyz/boundless | 193 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Mz PR Review
MaterializeInc/materialize
Local code review of current branch vs Materialize standards.
PR
boundless-xyz/boundless
Create or update a pull request for the current git changes.
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
More from dojoengine/dojo
Create A Plan
dojoengine/dojo
Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.
Dojo Contributing
dojoengine/dojo
Contributor workflow for dojoengine/dojo. An agent skill from dojoengine/dojo.
Related
Categories
Questions about Create PR
What does Create PR do?
Create or update a PR from current branch to main, watch CI, and address feedback. Create PR is an agent skill from dojoengine/dojo.
When should I use Create PR?
Create PR fits situations like: tasks that involve Pull requests.
How do I install Create PR in Claude Code?
Run `npx skills add dojoengine/dojo --skill create-pr -a claude-code`. Or copy the skill folder (.agents/skills/create-pr in dojoengine/dojo) into .claude/skills/create-pr in your project. Claude Code loads it when a task matches its description.
How do I install Create PR in Codex?
Run `npx skills add dojoengine/dojo --skill create-pr -a codex`. Or copy the skill folder (.agents/skills/create-pr in dojoengine/dojo) into .agents/skills/create-pr in your project. Codex loads it when a task matches its description.
Can I use Create PR in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dojoengine/dojo --skill create-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-pr, .gemini/skills/create-pr, .github/skills/create-pr and .opencode/skills/create-pr in your project.
What does Create PR need to run?
Going by SKILL.md and its folder, Create PR needs a shell for the scripts in its folder, the command-line tools its instructions call (git and gh) and credentials named GH_TOKEN and GITHUB_TOKEN. Our summary lists: A Bash shell; A credential in GITHUB_TOKEN.
Does Create PR access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create PR safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Create PR use?
Create PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Create PR use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Create PR?
Skills that share tags, products or a category with Create PR: Firewood Review (ava-labs/firewood, 153 stars), Mz PR Review (MaterializeInc/materialize, 6.4k stars), PR (boundless-xyz/boundless, 193 stars) and Finishing a Development Branch (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create PR?
dojoengine (a GitHub organization) maintains it in dojoengine/dojo, which has 478 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on May 6, 2026.
Source: dojoengine/dojo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.