菜单
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers `aster review --pr`, `--json`, `--stream`, `--comment`, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Zfinix/aster --skill aster-review-ci命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Reviewing a diff or feature for exploitable vulnerabilities before it ships. Use when asked to do a security review, when code touches auth, input handling, queries, files, URLs, crypto, or payments, and before merging changes that accept untrusted input.
Writing a plan the user can actually judge, and presenting it for approval with exit_plan_mode. Use when the user asks to plan first, when the work is large or irreversible enough that the approach should be agreed before any edit, and whenever you are about to call exit_plan_mode.
Control a whole Mac from one persistent Python session with screenshots, PID-targeted input, an animated virtual pointer, targeted Apple Accessibility, Apple Events, Browser Harness CDP, and filesystem access. Use for native, Electron, browser, dialog, file, or cross-app tasks without moving the physical cursor or forcing apps into the foreground.
基于 SOC 职业分类
正在显示 SKILL.md
| name | aster-review-ci |
| description | Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers `aster review --pr`, `--json`, `--stream`, `--comment`, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically. |
aster review reads a diff, hypothesizes defects, verifies them against the indexed repo, and reports findings. Everything is flag-driven; nothing requires a terminal.
aster review # current branch vs its base
aster review --range main..HEAD # explicit git range
aster review --diff changes.patch # a saved diff file
git diff main... | aster review --diff - # diff from stdin
aster review --pr 123 # fetch a GitHub PR's diff
--pr needs a token: --token, else GITHUB_TOKEN, else the one stored by aster login. The repo defaults to the origin remote; override with --repo owner/repo.
aster review --json # findings as one JSON array
aster review --stream # NDJSON progress events, one per line
Use --json in CI and pipe it to aster fix or your own tooling. --stream is for editors and UIs that want live progress. --tui is the interactive browser; never use it headless.
aster review --pr 123 --comment # post findings as inline PR comments
--comment implies --pr. Run it only when you intend to publish; the plain run is read-only.
aster review -i "src/**/*.rs" -x "**/generated/**" --min-confidence 0.7
-i/--include overrides include from aster.yaml; -x/--exclude adds to it. Both repeatable.--min-confidence <0.0-1.0> drops weak findings; falls back to aster.yaml.--no-index skips the symbol index for speed, at the cost of weaker verification. Prefer keeping the index in CI.--repo-root <DIR> points evidence retrieval at a checkout other than the cwd.- run: aster review --pr ${{ github.event.pull_request.number }} --comment --json > findings.json
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
ASTER_API_KEY: ${{ secrets.ASTER_API_KEY }}
The API key comes from ASTER_API_KEY (never from aster.yaml). An aster.yaml committed to the repo supplies models, analyzers, and filters; aster init -y writes a default one.