agy-superpowers 5.0.6 → 5.0.7

package/README.md

@@ -130,6 +130,29 @@ This workflow will:
 
 ---
 
+## Configuration
+
+Per-project settings live in `.agent/config.yml`. Create or edit this file in your project's `.agent/` folder:
+
+```yaml
+# .agent/config.yml
+
+# auto_commit: true | false
+# When true (default), Superpowers skills automatically commit after completing
+# tasks and writing design docs.
+# When false, all git commits and staging are skipped — files are left as
+# modified for you to commit manually.
+auto_commit: true
+```
+
+| Setting | Default | Description |
+|---|---|---|
+| `auto_commit` | `true` | AI auto-commits after tasks and design docs. Set to `false` to skip all commits. |
+
+This file is preserved across `/update-superpowers` runs.
+
+---
+
 ## Installation
 
 ### Using This Repo in Your Project

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agy-superpowers",
-  "version": "5.0.6",
+  "version": "5.0.7",
   "description": "Superpowers skills library for Google Antigravity agent — scaffold .agent/ with one command",
   "type": "module",
   "bin": {

package/template/agent/config.yml

@@ -0,0 +1,9 @@
+# Antigravity Superpowers — Project Config
+#
+# Configure per-project behavior by editing this file.
+# Skills read this file to determine how to behave in this project.
+
+# auto_commit: true | false
+# When true (default), AI automatically commits after completing tasks and writing design docs.
+# When false, all git commits and staging are skipped; files are left as modified for manual commit.
+auto_commit: false

package/template/agent/patches/skills-patches.md

@@ -0,0 +1,74 @@
+# Skill Patches
+
+Patches applied by AI during the `update-superpowers` workflow (Phase 2, Step 7).
+Each patch describes the *intent* of the change — AI finds the relevant section and rewrites it.
+Do not match text literally. Understand intent and adapt to current upstream wording.
+
+---
+
+## Patch: Platform Adaptation — using-superpowers
+
+**File:** `using-superpowers/SKILL.md`
+**Intent:** Remove all references to Claude Code, Gemini CLI, and Codex. Replace with a single
+Antigravity block: skills are read using `view_file` on `.agent/skills/<name>/SKILL.md`.
+Reference `references/antigravity-tools.md` for tool name mappings.
+The Platform Adaptation section should say this package is configured for Google Antigravity,
+with tool name equivalents in `references/antigravity-tools.md`.
+
+---
+
+## Patch: Platform mentions — executing-plans
+
+**File:** `executing-plans/SKILL.md`
+**Intent:** Replace any mentions of "Claude Code", "Codex", or other non-Antigravity platforms
+with "Antigravity". Example: "(such as Claude Code or Codex)" → "(such as Antigravity)".
+
+---
+
+## Patch: Skills path — writing-skills
+
+**File:** `writing-skills/SKILL.md`
+**Intent:** Replace platform-specific personal skill paths (`~/.claude/skills` for Claude Code,
+`~/.agents/skills/` for Codex) with the Antigravity path: `~/.agent/skills`.
+
+---
+
+## Patch: Visual companion platform blocks — brainstorming
+
+**File:** `brainstorming/visual-companion.md`
+**Intent:** Remove the Codex-specific server block. Replace Claude Code and Gemini CLI
+server startup blocks with a single Antigravity block:
+```bash
+# Launch the server normally
+scripts/start-server.sh --project-dir /path/to/project
+```
+
+---
+
+## Patch: Platform comment — dispatching-parallel-agents
+
+**File:** `dispatching-parallel-agents/SKILL.md`
+**Intent:** Remove the comment `// In Claude Code / AI environment` (or similar platform-specific
+inline comments). The code should work without platform-specific annotations.
+
+---
+
+## Patch: auto_commit flag — brainstorming
+
+**File:** `brainstorming/SKILL.md`
+**Intent:** Make the step that commits the design document to git conditional on `.agent/config.yml`:
+- Read `.agent/config.yml` before committing
+- If `auto_commit: true` (default): commit normally with `git add <path> && git commit -m "docs: add <topic> design spec"`
+- If `auto_commit: false`: skip commit and staging entirely. Print: "Skipping commit (auto_commit: false in .agent/config.yml). File is ready for manual commit."
+
+---
+
+## Patch: auto_commit flag — subagent-driven-development
+
+**File:** `subagent-driven-development/SKILL.md`
+**Intent:** Make the implementer subagent commit step conditional on `.agent/config.yml`:
+- Read `.agent/config.yml` before committing
+- If `auto_commit: true` (default): commit normally with `git add` + `git commit`
+- If `auto_commit: false`: skip commit and staging entirely. Print: "Skipping commit (auto_commit: false in .agent/config.yml). Files left as modified for manual commit."
+Update any diagram labels that mention "commits" to reflect this conditionality
+(e.g. "commits (if auto_commit: true)").

package/template/agent/skills/brainstorming/SKILL.md

@@ -114,7 +114,9 @@ digraph brainstorming {
 - Write the validated design (spec) to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
   - (User preferences for spec location override this default)
 - Use elements-of-style:writing-clearly-and-concisely skill if available
-- Commit the design document to git
+- **Commit the design document to git** — but first check `.agent/config.yml`:
+    - If `auto_commit: true` (default): run `git add <path> && git commit -m "docs: add <topic> design spec"`
+    - If `auto_commit: false`: skip commit and staging entirely. Print: "Skipping commit (auto_commit: false in .agent/config.yml). File is ready for manual commit."
 
 **Spec Review Loop:**
 After writing the spec document:

package/template/agent/skills/subagent-driven-development/SKILL.md

@@ -48,7 +48,7 @@ digraph process {
         "Dispatch implementer subagent (./implementer-prompt.md)" [shape=box];
         "Implementer subagent asks questions?" [shape=diamond];
         "Answer questions, provide context" [shape=box];
-        "Implementer subagent implements, tests, commits, self-reviews" [shape=box];
+        "Implementer subagent implements, tests, commits (if auto_commit: true), self-reviews" [shape=box];
         "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [shape=box];
         "Spec reviewer subagent confirms code matches spec?" [shape=diamond];
         "Implementer subagent fixes spec gaps" [shape=box];
@@ -67,8 +67,8 @@ digraph process {
     "Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
     "Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
     "Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
-    "Implementer subagent asks questions?" -> "Implementer subagent implements, tests, commits, self-reviews" [label="no"];
-    "Implementer subagent implements, tests, commits, self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
+    "Implementer subagent asks questions?" -> "Implementer subagent implements, tests, commits (if auto_commit: true), self-reviews" [label="no"];
+    "Implementer subagent implements, tests, commits (if auto_commit: true), self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
     "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" -> "Spec reviewer subagent confirms code matches spec?";
     "Spec reviewer subagent confirms code matches spec?" -> "Implementer subagent fixes spec gaps" [label="no"];
     "Implementer subagent fixes spec gaps" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [label="re-review"];
@@ -247,6 +247,10 @@ Done!
 - **Start code quality review before spec compliance is ✅** (wrong order)
 - Move to next task while either review has open issues
 
+**Before implementer commits:** Check `.agent/config.yml` for `auto_commit` setting.
+- If `auto_commit: true` (default): commit normally with `git add` + `git commit`
+- If `auto_commit: false`: skip commit and staging entirely. Print: "Skipping commit (auto_commit: false in .agent/config.yml). Files left as modified for manual commit."
+
 **If subagent asks questions:**
 - Answer clearly and completely
 - Provide additional context if needed

package/template/agent/workflows/update-superpowers.md

@@ -7,18 +7,26 @@ This workflow has two phases:
 - **Phase 2 (AI):** update the skill list in rules only — no content rewriting
 
 // turbo
-1. Run the update script:
+1. Preserve user config (if exists):
+   `[ -f .agent/config.yml ] && cp .agent/config.yml /tmp/agent-config-backup.yml && echo "Config backed up" || echo "No config to backup"`
+
+// turbo
+2. Run the update script:
    `bash .agent/.shared/update-superpowers.sh`
 
-   - If output ends with "Already up to date" → **STOP**. Nothing to do.
-   - If clone fails → **STOP**. Report the error to the user.
+   - If output ends with "Already up to date" → restore config if backed up (`[ -f /tmp/agent-config-backup.yml ] && cp /tmp/agent-config-backup.yml .agent/config.yml`), then **STOP**. Nothing to do.
+   - If clone fails → restore config if backed up, then **STOP**. Report the error to the user.
    - On success the script prints `SCRIPT_DONE:<new-tag>` — note the new tag and continue.
 
 // turbo
-2. Run the Antigravity patch script (breaks symlinks → real files, removes non-Antigravity tool refs):
+3. Run the Antigravity patch script (breaks symlinks → real files, removes non-Antigravity tool refs):
    `node scripts/patch-agent-skills.js`
 
-3. **Phase 2 — Update skill list in rules**
+// turbo
+4. Restore user config:
+   `[ -f /tmp/agent-config-backup.yml ] && cp /tmp/agent-config-backup.yml .agent/config.yml && echo "Config restored" || echo "No config to restore"`
+
+5. **Phase 2 — Update skill list in rules**
 
    List all skill folders now present in `.agent/skills/`.
    Open `.agent/rules/superpowers.md` and update **only the skills table**:
@@ -28,19 +36,30 @@ This workflow has two phases:
 
    If no skills were added or removed → skip, note "rules: no changes needed".
 
-4. **Phase 2 — New skills check**
+6. **Phase 2 — New skills check**
 
    For any skill in `.agent/skills/` that has no corresponding workflow in `.agent/workflows/`:
    - Read its `SKILL.md` `description` field.
    - Report it to the user: "New skill available: `<name>` — `<description>`. Create a workflow?"
    - Do NOT auto-create. Let the user decide.
 
+7. **Phase 2 — Apply skill patches from `.agent/patches/skills-patches.md`**
+
+   Read `.agent/patches/skills-patches.md`. For each patch entry:
+   - Open the target SKILL.md (path relative to `.agent/skills/`)
+   - Understand the *intent* described — do not match text literally
+   - Find the relevant section in the current file content
+   - Rewrite that section to match the intent, adapting to any upstream wording changes
+   - If the patch is already applied → skip, note "already applied"
+
+   Apply all patches before moving to the next step.
+
 // turbo
-5. Commit all changes from Phase 2:
+8. Commit all changes from Phase 2:
    `git add .agent/ && git commit -m "chore: sync .agent/ with superpowers <new-tag>"`
    (Skip commit if nothing changed.)
 
-6. Print summary:
+8. Print summary:
    ```
    ✅ Superpowers updated: <old-tag> → <new-tag>
    📦 Skills: <old-count> → <new-count>  (+new_skill / -removed_skill)