Run any Skill in Manus with one click

pull-remote

Stars0

Forks0

UpdatedMay 2, 2026 at 18:37

Use when the user wants to fetch or refresh remote rules — "pull rules from upstream", "update remote rules", "fetch latest rule version", "sync remote rules" — or right after editing `remote_rules` in `.autoreview/config.yaml`. Also use when a review fails because a referenced remote rule isn't yet on disk. Skip when no `remote_rules` are declared in config (the tool will warn and exit cleanly anyway).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

krzysztofdudek

krzysztofdudek/AutoReview

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

pull-remote

description

AutoReview Pull-Remote

Cross-platform. Snippets below use bash-style env-var syntax (${CLAUDE_PLUGIN_ROOT}). Claude Code's Bash tool runs Git Bash on Windows so these work as-is; on native PowerShell substitute $env:CLAUDE_PLUGIN_ROOT, on cmd use %CLAUDE_PLUGIN_ROOT%. Plugin requires Node ≥22 and git on PATH — those are the assumed binaries.

Fetch every remote_rules source declared in .autoreview/config.yaml. Each source is cloned into .autoreview/remote_rules/<name>/<ref>/ and gets a .autoreview-managed sentinel file.

Default — pull everything

node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/pull-remote.mjs

Pull one source by name

node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/pull-remote.mjs <source-name>

Use this when the user wants to refresh just one (--name shared in config → invoke with shared).

Refresh semantics

Re-running pull-remote is idempotent and the right way to update:

With ref: "v1.2.0" (a tag) — nothing changes unless the tag has been moved upstream. Bump ref in config and re-pull to switch versions.
With ref: "main" (a branch) — re-running picks up new commits from that branch.

After fetching — overlay validation

After a successful pull, warn if any remote_rules[<name>].overrides entry references a rule id that is not present in the freshly fetched ref:

[warn] override for 'corp-standards/legacy-rule' but rule absent in fetched ref v1.3.0

This means the upstream maintainer removed or renamed a rule you had overridden. The override config is kept (you may re-add the rule upstream or clean up the stale override), but the warning surfaces the drift. Use autoreview:override-rule to inspect and clean up stale overrides.

Safety mechanisms

Sentinel-protected wipe. The tool refuses to wipe a target dir containing non-markdown files unless a .autoreview-managed sentinel is present — protects against accidentally nuking a hand-edited local copy.
Hardened git invocation. git clone runs with GIT_CONFIG_NOSYSTEM=1 and core.hooksPath=/dev/null to prevent a hostile rule repo from running hooks on the user's machine.
URL/ref validation. URLs must use https://, http://, git://, ssh://, file://, a POSIX absolute path, or a Windows drive-letter absolute path. URLs starting with - are rejected (prevents --upload-pack=evil). Refs cannot contain .., leading /, or leading -.

Reporting

Report pulled <name>@<ref> -> .autoreview/remote_rules/<name>/<ref>/ per source, or the warning if no sources are declared. If a pull fails, surface the git error verbatim — usually it's an auth issue (wrong ref, private repo without credentials) that the user has to resolve outside the tool.

More from this repository

same repository

context

krzysztofdudek/AutoReview

Use when the agent has a concrete file path (about to edit `src/api/users.ts`) and needs the rules that apply to THAT path. Also use with no path to list all rule ids — triggers "what rules does this project have", "list all rules", "which rules exist", "show me the rules". Other triggers: "before I edit X, what rules apply?", a path reference without a review request. Skip when the agent wants an actual verdict (use autoreview:review); skip when no path yet and the user asks an abstract convention question (use autoreview:guide); skip when no `.autoreview/` exists — use autoreview:setup first.

2026-05-020

create-rule

krzysztofdudek/AutoReview

Use when user wants a new code convention rule added, regardless of phrasing — "add a rule", "enforce X", "forbid Y", "write a rule for Z", "create `.autoreview/rules/foo.md` with body ...". Once `.autoreview/` exists, invoke this skill for rule authoring even when the user asks to skip the wizard or specifies the exact file path and body — the wizard guards rule quality. Triggered whenever the user describes a pattern they want checked on every commit. Skip when no `.autoreview/` exists — use autoreview:setup first, then come back here.

2026-05-020

guide

krzysztofdudek/AutoReview

Use when the user asks a free-text question about a convention without a concrete file path ("how do I write a command handler here?", "what's the logging policy?"). The agent needs knowledge retrieval, not a review verdict. Skip when a file path is already known (use autoreview:context); skip when the user actually wants a pass/fail verdict on existing code (use autoreview:review); skip when no `.autoreview/` exists — use autoreview:setup first.

2026-05-020

history

krzysztofdudek/AutoReview

Use when the user asks about review verdicts over time — "what's been getting rejected", "rejection rate this week", "show recent reviews", "history of verdicts", "which rule fails most often", "show suppressed reviews", or filtering reviews by rule / file / date / verdict / tier / severity. Zero LLM cost — pure read of stored review records. Skip when the user wants a FRESH verdict (use autoreview:review) or when no `.autoreview/` exists (use autoreview:setup first).

2026-05-020

override-rule

krzysztofdudek/AutoReview

Use when user wants to adapt a remote rule's tier / triggers / severity / type WITHOUT forking the rule. Wizard for editing config.yaml's `remote_rules[].overrides` block. Triggers include "this corp rule is too noisy in my repo", "downgrade this rule to warning", "narrow this rule to only src/", "make this rule manual-only". Skip when the rule is local — local rules are owned by the user; edit the file directly. Skip when user wants to change rule body — that's a fork, not an overlay.

2026-05-020

precheck

krzysztofdudek/AutoReview

Use when user has drafted file content that is NOT on disk yet and wants a reviewer verdict before writing — explicit phrases like "would this pass review?", "check before I save", "will this be accepted?" with content not yet persisted. Costs 1 LLM call per rule. If the user references an existing file ("does this file pass", "check src/foo.ts") use autoreview:review instead — precheck requires unsaved draft content (pasted, or pointed at via `--content-file`). For plain "I'm about to edit file X", use autoreview:context (free) — don't precheck every edit. Skip when no `.autoreview/` exists — use autoreview:setup first.

2026-05-020

name

pull-remote

description

AutoReview Pull-Remote

Cross-platform. Snippets below use bash-style env-var syntax (${CLAUDE_PLUGIN_ROOT}). Claude Code's Bash tool runs Git Bash on Windows so these work as-is; on native PowerShell substitute $env:CLAUDE_PLUGIN_ROOT, on cmd use %CLAUDE_PLUGIN_ROOT%. Plugin requires Node ≥22 and git on PATH — those are the assumed binaries.

Fetch every remote_rules source declared in .autoreview/config.yaml. Each source is cloned into .autoreview/remote_rules/<name>/<ref>/ and gets a .autoreview-managed sentinel file.

Default — pull everything

node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/pull-remote.mjs

Pull one source by name

node ${CLAUDE_PLUGIN_ROOT}/scripts/bin/pull-remote.mjs <source-name>

Use this when the user wants to refresh just one (--name shared in config → invoke with shared).

Refresh semantics

Re-running pull-remote is idempotent and the right way to update:

With ref: "v1.2.0" (a tag) — nothing changes unless the tag has been moved upstream. Bump ref in config and re-pull to switch versions.
With ref: "main" (a branch) — re-running picks up new commits from that branch.

After fetching — overlay validation

After a successful pull, warn if any remote_rules[<name>].overrides entry references a rule id that is not present in the freshly fetched ref:

[warn] override for 'corp-standards/legacy-rule' but rule absent in fetched ref v1.3.0

Safety mechanisms

Sentinel-protected wipe. The tool refuses to wipe a target dir containing non-markdown files unless a .autoreview-managed sentinel is present — protects against accidentally nuking a hand-edited local copy.
Hardened git invocation. git clone runs with GIT_CONFIG_NOSYSTEM=1 and core.hooksPath=/dev/null to prevent a hostile rule repo from running hooks on the user's machine.
URL/ref validation. URLs must use https://, http://, git://, ssh://, file://, a POSIX absolute path, or a Windows drive-letter absolute path. URLs starting with - are rejected (prevents --upload-pack=evil). Refs cannot contain .., leading /, or leading -.