Skill

macroscope

Main Macroscope entrypoint. First check whether Macroscope correctness review already ran for the current local HEAD. If it did, triage unresolved PR comments. If it did not, run a local Macroscope review, triage streaming findings, fix the valid ones, and report what was addressed.

Install

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin prassoai-macroscope-local

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this as the canonical Macroscope router.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Use this as the canonical Macroscope router.

In Claude Code, this skill is /macroscope.

In Codex, plugin skills are namespaced, so this skill is /macroscope:macroscope.

This skill chooses between two different workflows:

PR path: Macroscope correctness review already ran for the current local HEAD. Use the PR-comment path only then. Do not run the Macroscope CLI.
CLI path: Macroscope correctness review has not run for the current local HEAD. Use the local CLI path.

Steps

1. Check whether Macroscope correctness review already ran for the current local HEAD

Start from the current local HEAD:

LOCAL_HEAD="$(git rev-parse HEAD)"

Then ask GitHub for the PR associated with the current branch and its status checks:

gh pr view --json number,title,url,headRefOid,statusCheckRollup 2>/dev/null

Treat Macroscope correctness review as having already run for the current local HEAD only when both of these are true:

gh pr view succeeds and headRefOid exactly matches LOCAL_HEAD.
statusCheckRollup contains a successful GitHub check run named Macroscope - Correctness Check. For compatibility, also accept the legacy name Review for correctness. The matching check should have status == "COMPLETED", conclusion == "SUCCESS", and a non-null completedAt.

If either condition fails, use the CLI path.

2. Route to the correct workflow

If Macroscope correctness review already ran for the current local HEAD:

Open ../triage-pr-comments/SKILL.md.
Follow that skill exactly.
Do not run macroscope codereview in parallel or as a supplement.
Stop after triage and point the user to ../respond-to-pr-comments/SKILL.md if they want you to act on the comments.

If Macroscope correctness review has not run for the current local HEAD:

Open ../local-review/SKILL.md.
Follow that skill exactly.
Keep the workflow closed-loop: triage streaming CLI findings, fix the valid ones, ignore false positives silently, and report only what you addressed.

3. Respect explicit user intent when it is narrower than the top-level Macroscope router

If the user explicitly asks to act on a previously triaged PR comment list, skip this router and use ../respond-to-pr-comments/SKILL.md.
If the user explicitly asks for a general review of the PR diff itself rather than comment triage, use ../review-pr/SKILL.md.