Worktrunk Tend CI Guidance
max-sixty/worktrunk
Adds Worktrunk-specific rules to the tend CI workflows: Codecov polling, Rust test commands, labels and review criteria for pull requests handled in CI.
Review code for quality, run linters, check test coverage, fix issues, and enforce gates.
Install Code Review Pi
$ npx skills add dimetron/pi-go --skill code-review-pi -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dimetron/pi-go code-review-pi --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/dimetron/pi-go.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pi-go/skills/code-review-pi .claude/skills/code-review-pi && 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 "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .claude/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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/dimetron/pi-go/tree/main/.pi-go/skills/code-review-piType 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 dimetron/pi-go --skill code-review-pi -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dimetron/pi-go code-review-pi --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimetron/pi-go.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.pi-go/skills/code-review-pi .agents/skills/code-review-pi && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .agents/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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 dimetron/pi-go --skill code-review-pi -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dimetron/pi-go code-review-pi --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimetron/pi-go.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.pi-go/skills/code-review-pi .cursor/skills/code-review-pi && 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 "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .cursor/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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/dimetron/pi-go.git --path .pi-go/skills/code-review-pi--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 dimetron/pi-go --skill code-review-pi -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dimetron/pi-go code-review-pi --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimetron/pi-go.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.pi-go/skills/code-review-pi .gemini/skills/code-review-pi && 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 "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .gemini/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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 dimetron/pi-go code-review-piInstalls 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 dimetron/pi-go --skill code-review-pi -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dimetron/pi-go.git skills-src && mkdir -p .github/skills && cp -r skills-src/.pi-go/skills/code-review-pi .github/skills/code-review-pi && 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 "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .github/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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 dimetron/pi-go --skill code-review-pi -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dimetron/pi-go code-review-pi --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dimetron/pi-go.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.pi-go/skills/code-review-pi .opencode/skills/code-review-pi && 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 "code-review-pi" agent skill from https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi into .opencode/skills/code-review-pi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review-pi", 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
code-review-pi- GitHub stars
- 207
- Token cost
- ~903 tokens
- SKILL.md length
- 446 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review code for quality, run linters, check test coverage, fix issues, and enforce gates.
- Works in 7 steps: Identify scope: Run git diff --name-only… → Run linters: Execute linters on target… → Run tests and check coverage → …
- Tasks that involve Code review
- SKILL.md covers Steps, Gates, Examples and Guidelines
- Calls go and git
What it does
Code Review Pi is an agent skill from dimetron/pi-go. Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review, Linting and formatting and Test coverage. The repository describes itself as: Go implementation of AI coding agent. The licence is MIT.
When your agent uses it
- Tasks that involve Code review
- Tasks that involve Linting and formatting
- Tasks that involve Test coverage
Example prompts
- “/code-review-pi”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify scope: Run git diff --name-only to find modified files. If there are changes, review only modified packages. If no uncommitted…
- Run linters: Execute linters on target packages
- Run tests and check coverage
- Review code quality: Read target files and check for
- Fix issues in parallel using subagents: For each package needing coverage fixes, spawn a subagent to work on it concurrently
- Verify gates: All gates must pass before reporting success
- Report: Write the final summary to ./specs/issues/003-code-review-pi/PROMPT.md and present
What it can do on your machine
Read from SKILL.md and the folder at commit 24d1f2b. 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
Shell commands in SKILL.md call:
gogit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code Review Pi loads about 903 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 446 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from dimetron/pi-go at commit 24d1f2b, republished under its MIT licence (© dimetron). 446 words, ~903 tokens.
Download SKILL.mdSave it as
.claude/skills/code-review-pi/SKILL.md (or your agent's skills folder).- name
- code-review-pi
- description
- Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
Code Review
Review code for quality, test coverage, and fix problems found.
The canonical output artifact for this skill is ./specs/issues/003-code-review-pi/PROMPT.md.
Only report success after writing the final review summary there.
Steps
Identify scope: Run
git diff --name-onlyto find modified files. If there are changes, review only modified packages. If no uncommitted changes, review all packages (./...).Run linters: Execute linters on target packages:
go vet ./...golangci-lint run --new-from-rev=HEAD~1 ./...(if available)
Run tests and check coverage:
go test -race -count=1 -coverprofile=coverage.out ./...go tool cover -func=coverage.out- Identify failing tests, functions with 0% coverage, packages below 80%
Review code quality: Read target files and check for:
- Missing tests for new/changed functions
- Error handling (missing checks, swallowed errors)
- Resource leaks (unclosed files, connections)
- Concurrency issues (race conditions, missing mutexes)
Fix issues in parallel using subagents: For each package needing coverage fixes, spawn a subagent to work on it concurrently:
- Use the
agenttool to spawn one subagent per package that needs test coverage improvement - Each subagent prompt: "Write tests for uncovered functions in package
<pkg>. Read the source files, identify untested functions using the coverage data, write table-driven tests covering happy path and error cases. Rungo test -race ./<pkg>/...to verify. NEVER delete existing tests." - While subagents write tests, fix linter warnings and code quality issues yourself
- Wait for all subagents to complete, then verify their work compiles
- Use the
Verify gates: All gates must pass before reporting success:
- GATE 1:
go build ./...— zero errors - GATE 2:
go vet ./...— zero warnings - GATE 3:
go test -race ./...— all tests pass - GATE 4:
go test -cover ./...— >= 80% per package - If any gate fails, fix and re-run until all pass
- GATE 1:
Report: Write the final summary to
./specs/issues/003-code-review-pi/PROMPT.mdand present:- Gates: PASS / FAIL for each
- Test results: pass/fail count
- Coverage: per-package percentages (before → after)
- Issues fixed with file:line references
Show full SKILL.md (138 more words)Show less
Gates
All gates are mandatory. Do not report success unless every gate passes.
| Gate | Command | Requirement |
|---|---|---|
| Build | go build ./... | Zero errors |
| Vet | go vet ./... | Zero warnings |
| Test | go test -race ./... | All pass |
| Coverage | go test -cover ./... | >= 80% per package |
Examples
/code-review— Full review: lint, test, coverage, parallel fix, verify gates
Guidelines
- If uncommitted changes exist, focus on modified packages
- If no changes, review all packages for full codebase quality check
- NEVER delete existing tests — only add or fix tests
- Use subagents to parallelize test writing across packages (one subagent per package)
- While subagents handle coverage, fix linter and quality issues in parallel
- Tests are mandatory: every new/changed exported function needs a test
- Table-driven tests preferred for Go code
- Test both happy path and error cases
- Fix issues directly — don't just report them
- Keep iterating until all gates pass
© dimetron, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .pi-go/skills/code-review-pi of dimetron/pi-go.
Open the folder on GitHubat commit 24d1f2b
Compare with similar skills
Code Review Pi 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 |
|---|---|---|---|---|---|---|
| Code Review Pi this skilldimetron/pi-go | 207 | — | ~903 | Automated safety check: Pass | MIT | |
| Worktrunk Tend CI Guidancemax-sixty/worktrunk | 9k | — | ~6.4k | Automated safety check: Pass | Custom licence | |
| Qt Cpp ReviewSerial-Studio/Serial-Studio | 7.2k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Qt Qml ReviewSerial-Studio/Serial-Studio | 7.2k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Qt6 QML Code Reviewerx-tools-author/x-tools | 1.1k | 1 repos | ~3.6k | Automated safety check: Pass | BSD-3-Clause | |
| Graph-Based Change Reviewtirth8205/code-review-graph | 32k | 1 repos | ~331 | Automated safety check: Pass | MIT |
Similar skills
Qt Cpp Review
Serial-Studio/Serial-Studio
Qt6/C++ deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.
Qt Qml Review
Serial-Studio/Serial-Studio
Qt6/QML deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.
Qt6 QML Code Reviewer
x-tools-author/x-tools
Runs a 47-rule deterministic QML linter, then six parallel deep-analysis passes over bindings, layout, loaders, delegates, states, and performance.
Graph-Based Change Review
tirth8205/code-review-graph
Reviews a change set using a code knowledge graph for risk scores, blast radius and test gaps, and ends with a merge recommendation.
Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
More from dimetron/pi-go
All 21 skills in this repoVhs E2E Gif
dimetron/pi-go
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit.
Agents Md
dimetron/pi-go
Generate AGENTS.md files for Go, Rust, TypeScript, and Java projects.
Bubbletea Testing
dimetron/pi-go
A skill your agent uses whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go.
Memory Index
dimetron/pi-go
Index a folder's contents into the MemPalace semantic memory for search and retrieval.
Nightly Session Watch
dimetron/pi-go
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still…
Osx Tuning
dimetron/pi-go
Tune macOS resource limits and sysctls for best performance with Go development, Docker/OrbStack, and Linux VMs.
Related
Categories
Questions about Code Review Pi
What does Code Review Pi do?
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Code Review Pi is an agent skill from dimetron/pi-go. Review code for quality, run linters, check test coverage, fix issues, and enforce gates.
When should I use Code Review Pi?
Code Review Pi fits situations like: tasks that involve Code review; tasks that involve Linting and formatting; tasks that involve Test coverage.
How do I install Code Review Pi in Claude Code?
Run `npx skills add dimetron/pi-go --skill code-review-pi -a claude-code`. Or copy the skill folder (.pi-go/skills/code-review-pi in dimetron/pi-go) into .claude/skills/code-review-pi in your project. Claude Code loads it when a task matches its description.
How do I install Code Review Pi in Codex?
Run `npx skills add dimetron/pi-go --skill code-review-pi -a codex`. Or copy the skill folder (.pi-go/skills/code-review-pi in dimetron/pi-go) into .agents/skills/code-review-pi in your project. Codex loads it when a task matches its description.
Can I use Code Review Pi 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 dimetron/pi-go --skill code-review-pi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review-pi, .gemini/skills/code-review-pi, .github/skills/code-review-pi and .opencode/skills/code-review-pi in your project.
What does Code Review Pi need to run?
Going by SKILL.md and its folder, Code Review Pi needs the command-line tools its instructions call (go and git).
Does Code Review Pi access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Code Review Pi 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. Review the folder before installing.
What licence does Code Review Pi use?
Code Review Pi is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Review Pi use?
About 903 tokens (SKILL.md is roughly 3.6k 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 Code Review Pi?
Skills that share tags, products or a category with Code Review Pi: Worktrunk Tend CI Guidance (max-sixty/worktrunk, 9k stars), Qt Cpp Review (Serial-Studio/Serial-Studio, 7.2k stars), Qt Qml Review (Serial-Studio/Serial-Studio, 7.2k stars) and Qt6 QML Code Reviewer (x-tools-author/x-tools, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Review Pi?
dimetron (a GitHub user) maintains it in dimetron/pi-go, which has 207 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 1, 2026.
Source: dimetron/pi-go on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.