Skip to content

Antigravity with Superpowers#682

Open
PhantomGM wants to merge 4 commits intoobra:mainfrom
PhantomGM:main
Open

Antigravity with Superpowers#682
PhantomGM wants to merge 4 commits intoobra:mainfrom
PhantomGM:main

Conversation

@PhantomGM
Copy link

Adds support for Google Antigravity via a triple-redundancy native skill discovery architecture. This PR introduces installation documentation and 13 Antigravity-adapted versions of the upstream skills.

Motivation and Context

Superpowers currently supports Claude Code, Cursor, Codex, and OpenCode, but not Antigravity. This PR extends support to Google Antigravity by mapping the agentic skill framework to Antigravity-native tools (like browser_subagent, task.md for artifacts, and view_file) instead of Claude Code tools (like TodoWrite or Skill).

How Has This Been Tested?

Tested locally on Windows using the Antigravity agent. Verified that the superpowers-bootstrap skill successfully loads via the global_workflows directory and accurately triggers context-appropriate adapted skills based on user requests.

Breaking Changes

None. These changes are strictly additive and contained within the new .antigravity/ directory, new docs/README.antigravity.md file, and an added section to the main README.md.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation (Not directly applicable, but acknowledged)
  • My code follows the repository's style guidelines
  • New and existing tests pass locally (N/A - markdown skills)
  • I have added appropriate error handling (N/A)
  • I have added or updated documentation as needed

Additional context

The integration uses a three-layer architecture to ensure reliable skill execution:

  1. Global workflow bootstrap: A custom superpowers-bootstrap inside Antigravity's global_workflows/ directory that fires at the start of every session based on a context trigger map.
  2. Antigravity-adapted skills: 13 skills stored in .antigravity/skills/ are installed to take priority. They are condensed and use Antigravity-native tool references so no mental translation is required by the agent. This includes subagent-development, an Antigravity-exclusive self-orchestration skill built to work around current subagent limitations.
  3. Full upstream skills: The skills/ directory is symlinked as a fallback reference for deep workflows, with tool mappings provided in README.antigravity.md for tools like TodoWrite.

@coderabbitai
Copy link

coderabbitai bot commented Mar 10, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 61243d17-b1be-4d65-a8a9-a8b789b95a75

📥 Commits

Reviewing files that changed from the base of the PR and between 4b42255 and 9a939b9.

📒 Files selected for processing (8)
  • .antigravity/INSTALL.md
  • .antigravity/skills/finishing-a-development-branch/SKILL.md
  • .antigravity/skills/requesting-code-review/SKILL.md
  • .antigravity/skills/test-driven-development/SKILL.md
  • .antigravity/skills/verification-before-completion/SKILL.md
  • .antigravity/skills/writing-workflows/SKILL.md
  • README.md
  • docs/README.antigravity.md
✅ Files skipped from review due to trivial changes (2)
  • .antigravity/skills/verification-before-completion/SKILL.md
  • .antigravity/skills/finishing-a-development-branch/SKILL.md
🚧 Files skipped from review as they are similar to previous changes (4)
  • docs/README.antigravity.md
  • .antigravity/skills/requesting-code-review/SKILL.md
  • .antigravity/INSTALL.md
  • .antigravity/skills/writing-workflows/SKILL.md

📝 Walkthrough

Walkthrough

Adds Antigravity integration and installation docs plus 13 new skill definition files under .antigravity/skills/* describing workflows (brainstorming, planning, execution, reviews, debugging, TDD, worktrees, subagent development, bootstrap discovery) and updates top-level README to reference Antigravity installation.

Changes

Cohort / File(s) Summary
Installation & Platform Docs
\.antigravity/INSTALL.md, docs/README.antigravity.md, README.md
New Antigravity installation guide (POSIX + PowerShell), verification, update/uninstall steps, and README updates adding Antigravity integration references.
Skill Discovery / Bootstrap
\.antigravity/skills/superpowers-bootstrap/SKILL.md
Adds a bootstrap discovery meta-skill mapping user intents to skill SKILL.md files, discovery precedence rules, and usage constraints.
Planning & Execution Workflows
\.antigravity/skills/writing-plans/SKILL.md, \.antigravity/skills/writing-workflows/SKILL.md, \.antigravity/skills/executing-plans/SKILL.md
New skills for writing structured plans/workflows and executing plans with task-level verification and stop conditions.
Design & Brainstorming
\.antigravity/skills/brainstorming/SKILL.md
Brainstorming workflow with one-question-at-a-time dialogue, 2–3 approaches with trade-offs, and an explicit hard gate requiring design approval before implementation.
Code Review Lifecycle
\.antigravity/skills/requesting-code-review/SKILL.md, \.antigravity/skills/receiving-code-review/SKILL.md
Standardized request/receive review processes, templates, and response patterns (READ→UNDERSTAND→VERIFY→EVALUATE→RESPOND→IMPLEMENT).
Quality, TDD & Verification
\.antigravity/skills/test-driven-development/SKILL.md, \.antigravity/skills/verification-before-completion/SKILL.md
TDD guidance (red/green/refactor) and an explicit verification-before-claim workflow and failure patterns.
Debugging & Investigation
\.antigravity/skills/systematic-debugging/SKILL.md
Structured four-phase systematic debugging workflow emphasizing root-cause analysis before fixes and phase-specific activities.
Implementation & Repo Safety
\.antigravity/skills/finishing-a-development-branch/SKILL.md, \.antigravity/skills/using-git-worktrees/SKILL.md, \.antigravity/skills/subagent-development/SKILL.md
Branch finishing options, git worktree creation/checks, and subagent-driven development with two-stage review gates and safety red flags.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Suggested labels

enhancement

Suggested reviewers

  • paseka10jaroslav-coder

Poem

🐇 I hopped in to map each skill and rule,
From plans to tests, each safety tool.
Worktrees planted, designs approved,
Bootstrap hums, the flow’s approved —
A rabbit cheers for a tidy tool! 🥕✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is vague and generic. While 'Antigravity with Superpowers' references the integration being added, it does not clearly convey the main change (adding Antigravity support via a skill discovery architecture). The title lacks specificity about what functionality is being introduced. Consider a more specific title such as 'Add Antigravity support with native skill discovery architecture' or 'Integrate Google Antigravity with adapted skills and bootstrap workflow' to better communicate the primary change.
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The description is comprehensive and well-related to the changeset. It clearly explains the motivation, architectural approach, testing performed, and the additive nature of changes without breaking existing functionality.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Nitpick comments (4)
docs/README.antigravity.md (1)

9-11: Add language specifier to fenced code block.

Markdown best practices recommend specifying a language for all fenced code blocks to improve rendering and accessibility.

📝 Proposed fix
-```
+```text
 Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md
 ```
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/README.antigravity.md` around lines 9 - 11, The fenced code block
missing a language specifier should be updated to include one (e.g., use "text"
or "markdown") so renderer and linters recognize it; locate the triple-backtick
block containing "Fetch and follow instructions from
https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md"
and change its opening fence to include the language token (for example,
```text) while keeping the existing content and closing fence unchanged.
.antigravity/skills/finishing-a-development-branch/SKILL.md (2)

20-20: Consider minor phrasing adjustment.

The phrase "requires typed" could be more natural as "requires typing" or "requires the user to type".

📝 Suggested phrasing improvement
-   4. Discard (requires typed "discard" confirmation)
+   4. Discard (requires typing "discard" confirmation)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.antigravity/skills/finishing-a-development-branch/SKILL.md at line 20,
Update the phrasing in the list item that currently reads '4. Discard (requires
typed "discard" confirmation)' to a more natural form such as '4. Discard
(requires typing "discard" to confirm)' or '4. Discard (requires the user to
type "discard" to confirm)'; locate the exact string 'requires typed "discard"
confirmation' in SKILL.md and replace it with one of the suggested alternatives
to improve clarity.

24-30: Add blank line before table for markdown consistency.

Markdown best practices suggest surrounding tables with blank lines for better rendering across different parsers.

📝 Proposed formatting fix
 ## Quick Reference
+
 | Option | Merge | Push | Keep Worktree | Delete Branch |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.antigravity/skills/finishing-a-development-branch/SKILL.md around lines 24
- 30, Add a blank line between the "## Quick Reference" heading and the table to
ensure proper Markdown rendering; edit the SKILL.md content around the
heading/table (the section containing the Markdown table starting with "| Option
| Merge | Push | Keep Worktree | Delete Branch |") and insert a single empty
line immediately after the "## Quick Reference" line.
README.md (1)

78-80: Add language specifier to fenced code block.

Consistent with other platforms' sections, this code block should specify a language for better rendering.

📝 Proposed fix
-```
+```text
 Fetch and follow instructions from https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md
 ```
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 78 - 80, The fenced code block that contains the line
"Fetch and follow instructions from
https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md"
needs a language specifier for consistent rendering; update that triple-backtick
fence (the fenced code block around the URL) to include a language such as
"text" (e.g., change ``` to ```text) so the block is rendered consistently with
other platform sections.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.antigravity/INSTALL.md:
- Around line 28-39: The instructions currently copy Antigravity-adapted skills
into ~/.agents/skills using the cp -r and PowerShell Copy-Item commands, leaving
renamed/removed skills stale and uninstall incomplete; replace that behavior by
either creating symlinks/junctions into ~/.agents/skills for the adapted skills
(instead of copying) or explicitly document and implement removal/reconciliation
during update and uninstall so copied directories are deleted or overwritten;
update the Step 3 text that references the cp -r and the PowerShell Copy-Item
commands and the related section (lines ~77-103) to show the symlink/junction
approach (and Windows equivalent) or to add clear removal steps for
updates/uninstalls.

In @.antigravity/skills/requesting-code-review/SKILL.md:
- Around line 24-38: The example block and table under "Review Request Format"
need valid markdown: change the untyped fenced block to a typed fence by adding
"md" after the opening backticks for the example list (the fenced block
containing the **What:**/**Why:**/etc. lines), ensure the fenced block is
properly closed on its own line, and add a blank line before the table header
and one after the table that starts with "| Priority | Action |" so the table is
separated from surrounding headings; update the fenced block and surrounding
spacing accordingly.

In @.antigravity/skills/test-driven-development/SKILL.md:
- Around line 40-48: Add blank lines before and after the "Common
Rationalizations" table so MarkdownLint accepts it: locate the "## Common
Rationalizations" heading and the table block (the pipe-delimited rows under
that heading) and insert one empty line between the heading and the table and
one empty line after the table end; ensure no other content is adjacent to the
table so the file passes docs lint.

In @.antigravity/skills/verification-before-completion/SKILL.md:
- Around line 13-21: The markdown fenced block under "The Gate Function" is
missing a language identifier which triggers markdownlint; update the opening
fence from ``` to ```text (i.e., add the language tag "text") so the block
becomes a labeled code fence; locate the fenced block containing the five-step
gate (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) and change only the opening
triple-backtick to include "text".

In @.antigravity/skills/writing-workflows/SKILL.md:
- Around line 15-31: The checklist requires "Cross-references to related
workflows" but the workflow template (the markdown frontmatter and headings: "##
Overview", "## When to Use", "## The Process", "## Quick Reference", "## Common
Mistakes") has no place for it; add a new heading "## Related Workflows" to the
template after "## Common Mistakes" (or alternatively remove the checklist item)
so the template and checklist match; update the template block in SKILL.md to
include the "## Related Workflows" section and ensure the checklist entry
remains accurate.

---

Nitpick comments:
In @.antigravity/skills/finishing-a-development-branch/SKILL.md:
- Line 20: Update the phrasing in the list item that currently reads '4. Discard
(requires typed "discard" confirmation)' to a more natural form such as '4.
Discard (requires typing "discard" to confirm)' or '4. Discard (requires the
user to type "discard" to confirm)'; locate the exact string 'requires typed
"discard" confirmation' in SKILL.md and replace it with one of the suggested
alternatives to improve clarity.
- Around line 24-30: Add a blank line between the "## Quick Reference" heading
and the table to ensure proper Markdown rendering; edit the SKILL.md content
around the heading/table (the section containing the Markdown table starting
with "| Option | Merge | Push | Keep Worktree | Delete Branch |") and insert a
single empty line immediately after the "## Quick Reference" line.

In `@docs/README.antigravity.md`:
- Around line 9-11: The fenced code block missing a language specifier should be
updated to include one (e.g., use "text" or "markdown") so renderer and linters
recognize it; locate the triple-backtick block containing "Fetch and follow
instructions from
https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md"
and change its opening fence to include the language token (for example,
```text) while keeping the existing content and closing fence unchanged.

In `@README.md`:
- Around line 78-80: The fenced code block that contains the line "Fetch and
follow instructions from
https://raw.githubusercontent.com/obra/superpowers/refs/heads/main/.antigravity/INSTALL.md"
needs a language specifier for consistent rendering; update that triple-backtick
fence (the fenced code block around the URL) to include a language such as
"text" (e.g., change ``` to ```text) so the block is rendered consistently with
other platform sections.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 1ade13b1-eaa4-4de5-b948-0493c3da7203

📥 Commits

Reviewing files that changed from the base of the PR and between 33e55e6 and 4b42255.

📒 Files selected for processing (16)
  • .antigravity/INSTALL.md
  • .antigravity/skills/brainstorming/SKILL.md
  • .antigravity/skills/executing-plans/SKILL.md
  • .antigravity/skills/finishing-a-development-branch/SKILL.md
  • .antigravity/skills/receiving-code-review/SKILL.md
  • .antigravity/skills/requesting-code-review/SKILL.md
  • .antigravity/skills/subagent-development/SKILL.md
  • .antigravity/skills/superpowers-bootstrap/SKILL.md
  • .antigravity/skills/systematic-debugging/SKILL.md
  • .antigravity/skills/test-driven-development/SKILL.md
  • .antigravity/skills/using-git-worktrees/SKILL.md
  • .antigravity/skills/verification-before-completion/SKILL.md
  • .antigravity/skills/writing-plans/SKILL.md
  • .antigravity/skills/writing-workflows/SKILL.md
  • README.md
  • docs/README.antigravity.md

@obra
Copy link
Owner

obra commented Mar 11, 2026

Hi, thanks for contributing this, but we're not going to be able to take a port that has custom versions of the skills.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants