Skip to content
Back to skills

Astra Review

ASecurity

Cross-vendor review on gpt-6-astra, medium. Same CLI lifecycle as codex-review. Use: /astra-review, 'have Astra review this'.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsshellbashgitapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add ryanportfolio/winuse-mcp --skill astra-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Astra Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Astra Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ryanportfolio-astra-review-winuse-mcp/badge)](https://www.skillsdirectory.com/skills/ryanportfolio-astra-review-winuse-mcp)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: astra-review
description: "Cross-vendor review on gpt-6-astra, medium. Same CLI lifecycle as codex-review. Use: /astra-review, 'have Astra review this'."
disable-model-invocation: true
---

# Astra review

Read `.claude/skills/codex-review/SKILL.md` and follow its complete execution contract: current local preflight, exact scope, unique run directory, source manifest, launch path (external-review first, selector fallback), process completion, report identity, finding verification, and honest attribution. This entrypoint changes only the defaults:

| Setting | Astra default |
|---|---|
| Model | `gpt-6-astra` |
| Effort | `medium`, regardless of diff size |
| Run directory prefix | `.tmp/astra-review-` |

Skip the newest-Sol check in `codex-review` Step 1; this entrypoint never swaps Astra for Sol. Honor an explicit user model/effort choice. Confirm supported local options before inference; a model identifier in this file is not proof of availability. `$ARGUMENTS` carries scope as in `codex-review`.

Example for a branch diff after creating a fresh `$RUN` directory (POSIX shell):

```bash
mkdir -p .tmp
RUN=$(mktemp -d .tmp/astra-review-XXXXXXXX)
git fetch origin main
BASE=$(git merge-base origin/main HEAD); HEAD_SHA=$(git rev-parse HEAD)
# External-review path (.agents/skills/external-review/SKILL.md exists):
codex exec review "Read .agents/skills/external-review/SKILL.md completely and follow it for this review of the branch diff: base $BASE, head $HEAD_SHA. Read the diff with git diff $BASE $HEAD_SHA. Leaf review: no agents, no nested reviews, no edits." -m gpt-6-astra -c model_reasoning_effort=medium -o "$RUN/report.md" < /dev/null > "$RUN/run.log" 2>&1
# Selector path (no external-review skill):
codex exec review --base origin/main -m gpt-6-astra -c model_reasoning_effort=medium -o "$RUN/report.md" < /dev/null > "$RUN/run.log" 2>&1
```

Commit and uncommitted prompts, the root-commit and dirty-tree rules, the skill-load and scope-identity checks, prompt escaping, and path attribution follow `codex-review`.

On PowerShell use a GUID-named directory and supported stdin/output redirection as described in `codex-review`. Distinct prefixes do not prevent collisions between two Astra invocations; every run must still be unique.

If Astra is unavailable, report that outcome. Do not silently inherit another model or attribute a fallback to Astra. A rejected Astra id is reported, never retried on another model; any other failure gets the one automatic retry from `codex-review`. A retry uses a new directory and reports its observed model/effort, or explicitly marks model resolution unverified. Keep lifecycle fixes in `codex-review` rather than forking them here.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.