agy-superpowers 5.1.5 → 5.1.6

package/package.json

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

package/template/agent/rules/debug-confirmation-policy.md

@@ -0,0 +1,34 @@
+---
+description: Require user confirmation before fixing any bug or error
+alwaysApply: true
+---
+
+# Debug Confirmation Policy
+
+<HARD-GATE>
+When you identify a bug, error, test failure, or any code that needs fixing —
+whether the user asked you to fix it, or you discovered it yourself —
+you MUST present your analysis and get user confirmation BEFORE writing any fix.
+
+## Required Analysis Report
+
+Present the following to the user:
+
+1. **Root Cause** — What is causing the issue and why
+2. **Evidence** — Error messages, stack traces, or code references that support your analysis
+3. **Proposed Fix** — Specific files and changes you plan to make
+4. **Risk Assessment** — What else could be affected by this fix
+
+Then ask: "Bạn đồng ý với phân tích và hướng fix này không?"
+
+## Wait for Confirmation
+
+- If user confirms → proceed with implementation
+- If user requests changes → revise analysis and re-present
+- If user rejects → stop and ask for guidance
+
+## DO NOT:
+- Write fix code before presenting analysis
+- Combine analysis + fix in one step
+- Skip this gate because the fix "seems obvious"
+</HARD-GATE>

package/template/agent/rules/language-matching.md

@@ -0,0 +1,32 @@
+---
+description: Match response language to user's language
+alwaysApply: true
+---
+
+# Language Matching Policy
+
+<HARD-GATE>
+You MUST respond in the same language the user is writing in.
+
+## Rules
+
+1. **Detect** — Identify the language of the user's most recent message.
+2. **Mirror** — Use that language for ALL natural-language content: explanations, descriptions, questions, analysis, summaries, and conversation.
+3. **Switch dynamically** — If the user switches language mid-conversation, switch immediately from your next response onward.
+
+## English Exceptions
+
+The following ALWAYS stay in English regardless of user language:
+
+- Code blocks, variable names, function names, class names
+- Commit messages
+- File names and file paths
+- Branch names
+- Technical terms with no widely-used equivalent (e.g., "refactor", "deploy", "middleware", "webhook")
+
+## DO NOT:
+- Respond in English when the user writes in another language
+- Mix languages in a single response (except for English exceptions above)
+- Default to English because "it's a technical topic"
+- Ignore language switches mid-conversation
+</HARD-GATE>

package/template/agent/skills/systematic-debugging/SKILL.md

@@ -167,6 +167,23 @@ You MUST complete each phase before proceeding to the next.
    - Ask for help
    - Research more
 
+### Confirmation Gate: Present Analysis Before Fixing
+
+<HARD-GATE>
+You MUST present your complete analysis to the user and get explicit confirmation
+BEFORE proceeding to Phase 4 (Implementation).
+
+**Present a summary containing:**
+1. **Root Cause** — from Phase 1
+2. **Pattern Analysis** — key differences found in Phase 2
+3. **Hypothesis** — your confirmed theory from Phase 3
+4. **Proposed Fix** — what you plan to change (files, functions, approach)
+
+Then ask: "Bạn đồng ý với phân tích và hướng fix này không?"
+
+Wait for user confirmation. Do NOT proceed to Phase 4 until confirmed.
+</HARD-GATE>
+
 ### Phase 4: Implementation
 
 **Fix the root cause, not the symptom:**