From agy
Internal contract for calling the local agy CLI runner from the agy bridge commands
How this skill is triggered — by the user, by Claude, or both
Slash command
/agy:agy-local-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Internal helper notes for the `/agy:*` commands. Not user-invokable.
Internal helper notes for the /agy:* commands. Not user-invokable.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/agy-run.sh" <command> [task...]
Commands: review, doc (read intent), fast-impl (write). result reads
.ai-runs/agy/ directly.
AGY has no hard read-only mode in headless -p: it writes anywhere on disk
regardless of --sandbox / --add-dir, governed only by global
~/.gemini/antigravity-cli/settings.json. There is no non-invasive per-run
override (project-local .gemini/settings.json is ignored; HOME override
breaks auth). Therefore:
--add-dir pointed at that workspace, and the workspace
is discarded afterward. The live working tree is never the target.review / doc keep only the text output and discard the workspace.fast-impl captures changes.diff; integration into the live tree is done by
Claude/the user after the user approves./grok:review instead (grok enforces --permission-mode plan at the CLI level).agy emits no JSON; stdout interleaves narration with the answer. We save raw
stdout to stdout.log and copy it verbatim to result.md (no clean extraction).
status: capture_failed = exit 0 with empty stdout (run interactively to debug).
<repo>/.ai-runs/agy/<job-id>/: prompt.md, context.txt, stdout.log,
result.md, stderr.log, status.json, and (fast-impl) changes.diff.
agy invocations.fast-impl diff without explicit user approval; verify it first
(AGY is a fast drafter, not a final authority)..ai-runs/ to their repo .gitignore.npx claudepluginhub jangisaac-dev/agy-plugin --plugin agyFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.