antigravity-maintainer-batch-release
Gives your AI agent ready-made instructions for a specific task, so it does it better and faster.
What it does
This tool helps keep code organized and up-to-date. It automates tasks like merging code, checking if everything is correct, and preparing new software releases.
When to use it
- ✓When you need to update multiple code changes at once.
- ✓To fix or merge code change requests.
- ✓When preparing to release a new software version.
Example of what to ask your AI
“Please help merge all accepted code changes and prepare the release for version 1.2.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool checks if the main code is clean and up-to-date. Then, it runs automatic checks and follows a secure process to merge changes and release new versions.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill antigravity-maintainer-batch-releaseOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/antigravity-maintainer-batch-release/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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:batchfor accepted source PRs. Do not substitute a raw merge API, generic GitHub skill, or generic push helper. - Let
automation/canonical-repo-stateown generated artifacts and contributor-credit convergence after the source batch. That lane runssync:repo-state, which now also recomputes the README## Top Contributorsleaderboards throughsync:top-contributors: never hand-edit those tables, and treat a stale ranking as a generator or exclusion-list defect instead. - Use
release:prepareandrelease:publishfor releases. They never authorize a directmainpush.
Source Checks
Before changing anything:
- Fetch
origin/main; prove the clean maintainer checkout is onmainand equalsorigin/main. - Inspect live PRs, issues, discussions in scope, Actions failures, Dependabot, CodeQL, secret scanning, and
npm auditwhere relevant. - Confirm current scripts from
package.jsonand the workflow files listed in Current CI workflow; do not rely on remembered CI or release behavior. - Capture user worktree status separately and keep those files out of maintainer commits.
Current CI workflow
Read .github/workflows/ci.yml, .github/workflows/skill-review.yml, .github/workflows/skillspector-advisory.yml, and their protected-base scripts on the exact task base. Job dependencies define execution order; file order and a green workflow badge do not define merge authority.
Required PR checks and independent review
| Lane | Actual sequence and evidence |
|---|---|
| Intake | pr-policy runs first. Ordinary source PRs use the exact protected-base classifier and its dependencies for fork safety and source-only policy. |
| Source validation | After pr-policy, source-validation checks sources, refreshes ephemeral generated state once, validates applicable references, runs the complete unsharded test suite and documentation security checks, and uploads the exact-head preview manifest. |
| Changed-skill evidence | Also after pr-policy, pr-evidence runs in parallel with source-validation. It publishes changed-skill evidence and a shadow decision manifest, then enforces deterministic regressions. Its advisory semantic-review state does not replace the separate skill-review result. |
| Artifact preview | artifact-preview waits for pr-policy and source-validation, verifies the source-preview manifest and its repository/head/workflow/run-attempt bindings, and does not regenerate ordinary source-PR artifacts. It does not wait for pr-evidence. |
| Semantic review | The separate skill-review.yml workflow fingerprints the complete changed skill trees. review means a passing Tessl result or valid identical-content reuse; manual-review-required needs the maintainer's semantic review and exact full-head attestation. It is independent of the required-CI DAG. |
| Static advisory scan | The separate PR-only skillspector-advisory.yml workflow runs evidence-ready, then skillspector-advisory. It waits for the latest GitHub Actions pr-evidence check for the same PR and exact head SHA, independently of source-validation, artifact-preview, and semantic review. |
…
FAQ
Can I push code directly to the main branch?
No, you should never push code directly to the main branch. The tool ensures all changes go through a secure review and merge process.
What are 'batch merges'?
These are when multiple code changes are combined at once, in an organized and secure way, to avoid conflicts and ensure stability.
Is this tool for ordinary contributions?
No, this tool is for maintenance and release tasks that require special permissions. Regular contributions should follow other processes.
Details
Original description by the author
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.
Popularity
- GitHub stars
- 48k
- Ranking position
- #2145
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC