Run local ClawSweeper exact-item or committed-range reviews without GitHub mutation.
61
71%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/local-clawsweeper-review/SKILL.mdUse this skill when someone wants read-only local ClawSweeper output before submitting, updating, or re-reviewing an issue or PR.
pnpm run review -- --local-only for an existing GitHub item, or
pnpm run review -- --local-range for a pre-submission committed range.apply-artifacts, apply-decisions, GitHub comment posting, or
merge/autofix commands unless the user explicitly asks for that mutation.OPENAI_API_KEY, CODEX_API_KEY, CODEX_ACCESS_TOKEN, GitHub
tokens, or Codex auth material.Prefer the current repository when its package.json name is
@openclaw/clawsweeper. Otherwise use a known clean local checkout:
C:\oc-work\clawsweeper-source~/Projects/clawsweeperInspect git status --short before making changes. If another ClawSweeper clone
is dirty or ambiguous, do not use it for the local review runner.
From the ClawSweeper checkout:
corepack enable
pnpm install
pnpm run build:all
pnpm run codex:local:checkIf the Codex check says the CLI is not logged in, have the operator authenticate their own Codex CLI. Device auth is the simplest shareable setup:
codex login --device-auth -c 'service_tier="fast"'For API-key setup, pass the key through the shell only for the login command and then clear it from the environment. Do not put the key in docs, scripts, shell history, or committed files.
PowerShell:
$env:OPENAI_API_KEY = Read-Host "OpenAI API key"
$env:OPENAI_API_KEY | codex login --with-api-key -c 'service_tier="fast"'
Remove-Item Env:OPENAI_API_KEYPOSIX shell:
printf '%s' "$OPENAI_API_KEY" | codex login --with-api-key -c 'service_tier="fast"'
unset OPENAI_API_KEYIf the wrong Codex binary is used, set CODEX_BIN in the local shell for that
run. Otherwise, --local-only uses the first spawnable codex command on
PATH, including on Windows. If no Windows PATH command is spawnable, it falls
back to the installed Codex Desktop binary.
By default, an exact local PR review manages its own target checkout under
artifacts/local-review-<pr-number>/target.
By default, --local-range reviews the clean checkout where the command was
invoked. It does not manage or switch that checkout. Pass --target-dir when
the branch to review is elsewhere.
Pass --target-dir when the operator wants to review an existing checkout or
an issue.
Use a clean target checkout of the repository being reviewed. Prefer a dedicated review checkout if the normal worktree is dirty:
C:\oc-work\clawsweeper-local-target-openclaw../openclawBefore reviewing against main, update the target checkout only when it is
clean:
git -C <target-dir> status --short
git -C <target-dir> fetch origin main
git -C <target-dir> switch main
git -C <target-dir> pull --ff-only origin mainDo not switch branches, pull, or overwrite files in a dirty target checkout.
Use the exact issue or PR number. If the number is not provided and the current
branch has an open PR, use gh pr view --json number,url,headRefOid to identify
it.
From the ClawSweeper checkout:
pnpm run review -- --local-only --item-number <pr-number>To use a supplied checkout or review an issue:
pnpm run review -- --local-only \
--item-number <issue-or-pr-number> \
--target-dir <target-dir>To review committed branch work before a PR exists:
pnpm run review -- --local-range \
--target-repo <owner/repo> \
--base origin/mainThe range is merge-base(<base>, HEAD)..HEAD. It must be clean and contain at
least one commit beyond the base. This path withholds GitHub credentials,
isolates cached gh auth, disables web search, and skips host-side URL/media
preprocessing. It still calls the configured Codex model service; do not call it
air-gapped or fully network-offline.
The exact local command prints a human-readable progress summary by default. Add
--verbose only when debugging checkout, selection, or Codex process details.
For quick smoke tests, lower --batch-size, --shard-count, --max-pages, and
--codex-timeout-ms, but label the result as a smoke run rather than a full
local review.
The default OpenClaw report is written to:
<artifact-dir>/<issue-or-pr-number>.mdRead the artifact and summarize:
review_statusmain_shapull_head_sha for PRsIf the failure is Codex auth, stop after providing the local setup command. If the failure is runner/runtime behavior, include the artifact path and a concise stderr or log summary.
Before reporting success:
review --local-only or review --local-range.main_sha and PR head SHA when available.45c34fe
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.