Agent skill · software engineering · sickn33
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
Why this skill is useful
Adds executable scripts for repository maintenance and release processes that are not commonly found in public documentation.
What it needs
Requires npm installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Antigravity Maintainer Batch Release When to Use Use this skill for repository-wide AAS maintenance, maintainer-side PR repair or merge batches, canonical synchronization, AAS Core or Workbench changes, protected releases, and hosted catalog or legacy redirect infrastructure. Do not use it for ordinary contribution work that does not require maintainer privileges or canonical convergence. Protected-Main Contract Treat the repository root containing this skill as pull-request-only: Read AGENTS.md, .github/MAINTENANCE.md, and current maintainer docs before mutation. Never commit or push directly to main, even when the user says “push to main.” That phrase names the final target state. Preserve unrelated dirty work. Use a clean temporary clone or a topic branch for maintainer changes. Use npm run merge:batch for accepted source PRs. Do not substitute a raw merge API, generic GitHub skill, or generic push helper. Let automation/canonical-repo-state own generated artifacts and contributor-credit convergence after the source batch. That lane runs sync:repo-state, which now also recomputes the README ## Top Contributors leaderboards through sync:top-contributors: never hand-edit those tables, and treat a stale ranking as a generator or exclusion-list defect instead. Use release:prepare and release:publish for releases. They never authorize a direct main push. Source Checks Before changing anything: 1. Fetch origin/main; prove the clean maintainer checkout is on main and equals origin/main. 2. Inspect live PRs, issues, discussions in scope, Actions failures, Dependabot, CodeQL, secret scanning, and npm audit where relevant. 3. Confirm current scripts from package.json and the workflow files listed in Current CI workflow; do not rely on remembered CI or release behavior. 4. Capture user worktree status separately and keep those files out of maintainer commits. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/antigravity-maintainer-batch-release--b75057