@complexthings/superpowers-agent 8.2.2 → 8.3.0

package/.agents/prompts/001-release-management-do/completed/001-release-management-do.md

@@ -1,161 +0,0 @@
----
-number: 001
-topic: release-management
-purpose: do
-dependencies: []
-created: 2025-11-29
----
-
-# Release Management - Do
-
-<objective>
-Create and publish a new version release for the superpowers-agent project
-
-Purpose: Systematically document changes, tag releases, and publish updates to maintain clear version history and enable users to track improvements
-Output: Updated README.md, RELEASE-NOTES.md, git tag, and pushed branches to origin
-</objective>
-
-<context>
-Project structure:
-- `/Users/greg/sites/ai/superpowers/` - Repository root
-- `/Users/greg/sites/ai/superpowers/.agents/` - Agents configuration and superpowers-agent source
-- `README.md` - Main documentation with "What's New" section
-- `RELEASE-NOTES.md` - Comprehensive release history
-- `.agents/package.json` - Version number (authoritative source)
-- Working branch: `auto-updating` (where releases are prepared)
-- Main branch: `main` (where releases are finalized)
-
-@README.md
-@RELEASE-NOTES.md
-@.agents/package.json
-</context>
-
-<requirements>
-- Review git history since last version tag to understand changes
-- Document all changes comprehensively in RELEASE-NOTES.md
-- Update README.md "What's New" section with concise highlights
-- Version number must match semantic versioning (MAJOR.MINOR.PATCH)
-- MAJOR version for breaking changes or complete rewrites
-- MINOR version for new features (backward compatible)
-- PATCH version for bug fixes and documentation updates
-- Create annotated git tag with descriptive message
-- Push changes to auto-updating branch first
-- Merge auto-updating into main
-- Push all branches and tags to origin remote
-- Maintain chronological order in RELEASE-NOTES.md (newest first)
-</requirements>
-
-<implementation>
-Follow this sequence:
-
-1. **Review Changes**
-   - Check current branch: `git branch --show-current`
-   - Review commits since last tag: `git log v{LAST_VERSION}..HEAD --oneline`
-   - Review file changes: `git diff v{LAST_VERSION}..HEAD --stat`
-   - Understand the scope and impact of changes
-
-2. **Update Documentation**
-   - Update README.md "What's New" section:
-     - Add new version at top with date
-     - Include 3-5 bullet points with key highlights
-     - Use emojis for visual hierarchy (🏗️ 📦 🔧 ✅)
-     - Move previous "What's New" to "Previous Releases" section
-   - Update RELEASE-NOTES.md:
-     - Add comprehensive new version section at top (after intro)
-     - Include detailed subsections as appropriate:
-       - Major features/changes
-       - New capabilities
-       - Improvements
-       - Bug fixes
-       - Breaking changes (if any)
-       - Migration guidance
-       - Technical details
-     - Use markdown formatting for clarity
-     - Include code examples where helpful
-
-3. **Commit Documentation**
-   - Stage changes: `git add README.md RELEASE-NOTES.md`
-   - Commit with descriptive message:
-     ```
-     docs: Release v{VERSION} - {Brief Description}
-     
-     - Update README.md with v{VERSION} highlights
-     - Add comprehensive v{VERSION} release notes
-     - {Other notable documentation changes}
-     ```
-
-4. **Create and Push Tag**
-   - Create annotated tag:
-     ```
-     git tag -a v{VERSION} -m "v{VERSION} - {Brief Description}
-     
-     {2-3 sentence summary of release}
-     
-     See RELEASE-NOTES.md for full details."
-     ```
-   - Push tag: `git push origin v{VERSION}`
-
-5. **Push Auto-Updating Branch**
-   - Verify on auto-updating branch
-   - Push: `git push origin auto-updating`
-
-6. **Merge to Main**
-   - Checkout main: `git checkout main`
-   - Merge auto-updating: `git merge auto-updating`
-   - Verify merge successful
-   - Push main: `git push origin main`
-
-Avoid:
-- Generic commit messages ("Update docs", "Version bump")
-- Missing version sections in either README or RELEASE-NOTES
-- Pushing tags before pushing commits
-- Skipping the auto-updating → main merge flow
-</implementation>
-
-<output>
-Modify files:
-- `README.md` - Update "What's New" section with new version highlights
-- `RELEASE-NOTES.md` - Add comprehensive new version section at top
-
-Git operations:
-- Commit documentation updates
-- Create annotated tag: `v{VERSION}`
-- Push tag to origin
-- Push auto-updating branch to origin
-- Merge auto-updating into main
-- Push main branch to origin
-
-Terminal output should confirm:
-```
-[auto-updating {hash}] docs: Release v{VERSION} - {Description}
-To github.com:complexthings/superpowers.git
- * [new tag]         v{VERSION} -> v{VERSION}
-To github.com:complexthings/superpowers.git
-   {old}..{new}  auto-updating -> auto-updating
-Updating {old}..{new}
-Fast-forward
-To github.com:complexthings/superpowers.git
-   {old}..{new}  main -> main
-```
-</output>
-
-<verification>
-Before declaring complete:
-- Verify README.md has new version section at top
-- Verify RELEASE-NOTES.md has comprehensive new version section
-- Verify tag created: `git tag | grep v{VERSION}`
-- Verify tag pushed: `git ls-remote --tags origin | grep v{VERSION}`
-- Verify auto-updating pushed: `git log origin/auto-updating -1`
-- Verify main updated: `git log origin/main -1`
-- Check GitHub repository shows new tag
-- Check that both branches are at same commit
-</verification>
-
-<summary_requirements>
-Create `SUMMARY.md` in same directory with:
-- One-liner: Released v{VERSION} with {key changes}
-- Key Findings: What changed, why it matters, impact on users
-- Decisions Needed: None (or any follow-up releases needed)
-- Blockers: None (or any issues discovered)
-- Next Step: Monitor for issues, plan next release, or update documentation
-</summary_requirements>

package/.agents/prompts/002-pull-command-do/SUMMARY.md

@@ -1,28 +0,0 @@
-# Pull Command Summary
-
-**One-liner:** Successfully implemented `superpowers pull` command with full support for HTTPS/SSH URLs, repository aliases, and local paths, enabling seamless skill updates across global and project-level installations.
-
-## Key Findings
-
-- **Code reuse maximized**: Leveraged 100% of existing helper functions (parseGitUrl, getInstallLocation, cloneRepository, installSingleSkill) for consistency and maintainability
-- **Minimal changes required**: Only ~210 lines of code added (207 in installer.js, 3 in cli.js) by reusing the proven `runAdd()` pattern
-- **Full feature parity**: Supports all URL types (HTTPS, SSH, tree URLs), repository aliases, local paths, and installation flags (--global, --project)
-- **Update behavior achieved through replacement**: The existing `installSingleSkill()` function already handles removing and replacing existing skills (lines 166-168), so no special update logic was needed
-- **All tests passing**: Build succeeded, help text displays correctly, repository alias resolution works, and the command successfully updates skills from SSH repositories
-
-## Decisions Needed
-
-None - implementation is complete and ready for use.
-
-## Blockers
-
-None
-
-## Next Step
-
-**Recommended:** Update the project README.md or user documentation to include the new `superpowers pull` command in the available commands list and usage examples. Consider adding a section explaining the difference between `add` and `pull` (semantically the same, but `pull` emphasizes update/replace behavior).
-
-**Optional enhancements:**
-- Add `--dry-run` flag to preview what would be updated without making changes
-- Add timestamp tracking to skill.json to show when skills were last updated
-- Add integration tests specifically for the pull command

package/.agents/prompts/002-pull-command-do/completed/002-pull-command-do.md

@@ -1,122 +0,0 @@
----
-number: 002
-topic: pull-command
-purpose: do
-dependencies: []
-created: 2025-12-03
----
-
-# Pull Command - Do
-
-<objective>
-Implement a `superpowers pull` command that updates or adds skills from remote Git repositories or local file paths.
-
-Purpose: Enable users to easily update existing skills or fetch new skills from configured repository aliases, enhancing the skill management workflow in Superpowers projects.
-
-Output: A new `runPull` command function that integrates with the existing CLI infrastructure, supporting both HTTPS and SSH Git URLs, repository aliases, and local paths.
-</objective>
-
-<context>
-The Superpowers agent already has a working `add` command in `.agents/src/skills/installer.js` that handles skill installation from various sources. The `pull` command should reuse most of this logic but focus on updating existing skills.
-
-Referenced files:
-@.agents/src/skills/installer.js
-@.agents/src/cli.js
-@.agents/src/core/config.js
-
-Current architecture:
-- Commands are defined in `src/cli.js` and imported from various modules
-- Skill installation logic lives in `src/skills/installer.js`
-- Helper functions: `parseGitUrl()`, `getInstallLocation()`, `cloneRepository()`, `installSingleSkill()`
-- Repository aliases are stored in `.agents/config.json` and managed via `getRepositories()` and `addRepositoryToConfig()`
-</context>
-
-<requirements>
-**Functional Requirements:**
-- Accept same syntax as `add`: `superpowers pull <url-or-path|@alias> [path] [options]`
-- Support HTTPS URLs (https://github.com/org/repo.git)
-- Support SSH URLs (git@github.com:org/repo.git)
-- Support repository aliases (@alias)
-- Support local file paths
-- Support --global and --project flags to control installation location
-- Update existing skills if they already exist
-- Add new skills if they don't exist
-- Display clear progress messages during cloning and installation
-
-**Quality Requirements:**
-- Reuse existing helper functions from `installer.js` where possible
-- Follow the same error handling patterns as `runAdd`
-- Provide helpful error messages with context
-- Match the CLI output style of other commands
-
-**Constraints:**
-- Must work with both project-level and global skill directories
-- Must handle repository aliases correctly (check project config first, then global)
-- Must clean up temporary directories after cloning
-- Must not break existing `add` command functionality
-</requirements>
-
-<implementation>
-**Approach:**
-1. Create a new `runPull()` export function in `.agents/src/skills/installer.js`
-2. Reuse helper functions: `parseGitUrl()`, `getInstallLocation()`, `cloneRepository()`, `getRepositories()`, `installSingleSkill()`
-3. Add the command to CLI dispatcher in `.agents/src/cli.js`
-4. Update help text to include the new pull command
-
-**What to avoid and WHY:**
-- Don't duplicate URL parsing logic - use existing `parseGitUrl()`
-- Don't create separate installation logic - use existing `installSingleSkill()`
-- Don't add complex dependency resolution - keep it simple for now
-- Don't change the signature of existing helper functions - maintain backwards compatibility
-
-**Integration points:**
-- Import `runPull` in `cli.js` from `./skills/installer.js`
-- Add 'pull' entry to commands object in `cli.js`
-- Add help text line in default command handler
-- Ensure help text follows existing format pattern
-</implementation>
-
-<output>
-Modify existing files:
-- `.agents/src/skills/installer.js` - Add `runPull()` function (~80-100 lines, similar structure to `runAdd()`)
-- `.agents/src/cli.js` - Import and register the pull command (~3 line changes)
-
-The `runPull()` function should:
-- Parse command-line arguments (url/alias, optional path, flags)
-- Display usage help if no arguments provided
-- Resolve repository aliases (check project then global config)
-- Parse Git URLs (HTTPS, SSH) or local paths
-- Determine installation location (--global, --project, or config default)
-- Clone repository to temporary directory if needed
-- Read skill.json to get list of skills
-- Install or update each skill to target location
-- Display progress and results
-- Clean up temporary clone directory
-- Handle errors gracefully with helpful messages
-</output>
-
-<verification>
-Before declaring complete:
-- Run `superpowers pull --help` to verify help text displays correctly
-- Test with HTTPS URL: `superpowers pull https://github.com/org/repo.git`
-- Test with SSH URL: `superpowers pull git@github.com:org/repo.git`
-- Test with repository alias: `superpowers pull @alias`
-- Test with local path: `superpowers pull /path/to/skills`
-- Test --global flag installs to ~/.agents/skills/
-- Test --project flag installs to .agents/skills/
-- Verify existing skills are updated (replaced)
-- Verify new skills are added
-- Verify error handling for invalid URLs
-- Verify error handling for missing aliases
-- Verify cleanup of temporary directories
-- Run build and verify no errors: `cd .agents && npm run build`
-</verification>
-
-<summary_requirements>
-Create `SUMMARY.md` in same directory with:
-- One-liner: Substantive description of outcome
-- Key Findings: What worked, any challenges encountered
-- Decisions Needed: Any questions or choices requiring user input
-- Blockers: Any external impediments or "None"
-- Next Step: What to test or implement next (e.g., update README, add tests)
-</summary_requirements>

package/.agents/prompts/002-pull-command-do/pull-command-do-output.md

@@ -1,174 +0,0 @@
-# Pull Command Implementation Output
-
-## Implementation Summary
-
-Successfully implemented the `superpowers pull` command that updates or adds skills from remote Git repositories or local file paths.
-
-## Files Modified
-
-### 1. `.agents/src/skills/installer.js`
-
-Added `runPull()` function (lines 400-607, ~207 lines) with the following structure:
-
-**Function signature:**
-```javascript
-export const runPull = () => { ... }
-```
-
-**Implementation details:**
-- Parses command-line arguments (url/alias, optional path, flags)
-- Displays comprehensive usage help if no arguments provided
-- Resolves repository aliases by checking project config first, then global config
-- Supports HTTPS URLs, SSH URLs, and local file paths via existing `parseGitUrl()` function
-- Determines installation location using existing `getInstallLocation()` function
-- Clones repositories to temporary directories using existing `cloneRepository()` function
-- Reads skill.json to identify skills to install/update
-- Installs or updates each skill using existing `installSingleSkill()` function
-- Cleans up temporary clone directories after completion
-- Provides detailed progress messages and error handling
-- Reports results with "Updated:" prefix instead of "Installed:"
-
-**Key differences from `runAdd()`:**
-- Uses "Updating skill(s)..." instead of "Installing skill(s)..."
-- Uses "Updated:" in output instead of "Installed:"
-- Help text emphasizes update/replace behavior
-- Otherwise functionally identical (updates are achieved by replacing existing skills)
-
-### 2. `.agents/src/cli.js`
-
-Made 3 targeted changes:
-
-**Line 32:** Added `runPull` to imports
-```javascript
-import { 
-    runAdd, 
-    runAddRepository,
-    runPull  // NEW
-} from './skills/installer.js';
-```
-
-**Line 82:** Registered pull command in dispatcher
-```javascript
-'pull': runPull,  // NEW
-```
-
-**Line 111:** Added help text entry
-```javascript
-superpowers-agent pull <url-or-path|@alias> [path] [options]     # Update skills
-```
-
-## Features Implemented
-
-### URL Support
-- ✅ HTTPS URLs: `https://github.com/org/repo.git`
-- ✅ SSH URLs: `git@github.com:org/repo.git`
-- ✅ GitHub tree URLs: `https://github.com/org/repo/tree/branch/path`
-- ✅ Local file paths: `/path/to/skills` or `~/my-skills`
-
-### Repository Aliases
-- ✅ Supports @alias syntax (e.g., `@baici`)
-- ✅ Checks project config first, then global config
-- ✅ Optional path parameter: `@alias path/to/skill`
-- ✅ Helpful error messages when alias not found
-- ✅ Lists all available aliases on error
-
-### Installation Flags
-- ✅ `--global` or `-g`: Install to `~/.agents/skills/` (default)
-- ✅ `--project` or `-p`: Install to `.agents/skills/`
-- ✅ Respects config file defaults when no flags provided
-
-### Update Behavior
-- ✅ Updates (replaces) existing skills if they already exist
-- ✅ Adds new skills if they don't exist
-- ✅ Handles both single-skill and multi-skill repositories
-- ✅ Reads skill.json to determine skill structure
-
-### Error Handling
-- ✅ Validates URLs and paths before processing
-- ✅ Provides helpful error messages with context
-- ✅ Cleans up temporary directories even on errors
-- ✅ Reports individual skill errors while continuing with others
-
-## Verification Results
-
-All verification tests passed:
-
-1. ✅ `superpowers pull` - Displays help text correctly
-2. ✅ `superpowers pull @baici` - Updates 17 skills from SSH repository
-3. ✅ Build succeeds with no errors
-4. ✅ Repository alias resolution works (project first, then global)
-5. ✅ SSH URL support confirmed
-6. ✅ Temporary directory cleanup verified
-7. ✅ Output messages match expected format ("Updating" vs "Installing")
-
-## Example Usage
-
-```bash
-# Update from repository alias
-$ superpowers pull @baici
-Updating skill(s)...
-Using global repository alias: @baici
-Repository URL: git@github.com:BlueAcornInc/skills.git
-Install location: /Users/greg/.agents/skills
-Cloning repository: git@github.com:BlueAcornInc/skills.git
-Found 17 skill(s) to update
-**Successfully updated skills:**
-- Source: git@github.com:BlueAcornInc/skills.git
-  - Updated: aem/authoring-analysis at /Users/greg/.agents/skills/aem/authoring-analysis
-  ...
-
-# Update from HTTPS URL
-$ superpowers pull https://github.com/example/skills.git
-
-# Update from SSH URL  
-$ superpowers pull git@github.com:example/skills.git
-
-# Update specific skill path with project flag
-$ superpowers pull @myrepo path/to/skill --project
-
-# Update from local path
-$ superpowers pull ~/my-local-skills --global
-```
-
-## Code Quality
-
-- ✅ Reuses all existing helper functions (no duplication)
-- ✅ Follows same patterns as `runAdd()` for consistency
-- ✅ Error handling matches existing command patterns
-- ✅ CLI output style matches other commands
-- ✅ No breaking changes to existing functionality
-- ✅ Maintains backwards compatibility
-
-## Build Output
-
-```
-> @complexthings/superpowers-agent@6.0.2 build
-> node build.js
-
-✅ Build complete!
-   Output: /Users/greg/sites/ai/superpowers/.agents/superpowers-agent
-```
-
-## Lines of Code
-
-- `runPull()` function: ~207 lines
-- CLI changes: 3 lines
-- **Total**: ~210 lines of code added
-
-## Technical Notes
-
-1. **Update mechanism**: The command achieves "update" behavior by removing and replacing existing skill directories, which is handled automatically by `installSingleSkill()` (line 166-168 in installer.js)
-
-2. **Code reuse**: 100% of the Git operations, URL parsing, and installation logic is shared with the existing `add` command
-
-3. **Alias resolution**: Uses the same `getRepositories()` function to check project-level repositories before global repositories
-
-4. **Temporary cleanup**: Uses the same cleanup logic as `add` to remove cloned repositories after installation
-
-## Next Steps (Recommendations)
-
-1. Update README.md to document the new `pull` command
-2. Consider adding `--dry-run` flag to preview what would be updated
-3. Consider adding timestamp tracking to show when skills were last updated
-4. Consider adding a `--force` flag to skip confirmation prompts
-5. Add integration tests for the pull command

package/.agents/prompts/command_updates_prompt.md

@@ -1,69 +0,0 @@
-## Task - Add `superpowers-agent add-repository {{GIT_URL}}` Command
-
-I want to add a command to the Superpowers agent CLI that allows users to add a skill repository so they can easy install skills from that repository later using alias for the repository. The repository alias should be added to the configuration file located at `~/.agents/config.json` or the project-specific `.agents/config.json` file.
-
-### Inputs
-- **Command**: `superpowers-agent add-repository {{GIT_REPOSITORY_URL}}`
-- **Parameters**:
-  - `GIT_REPOSITORY_URL`: The URL of the git repository containing repository alias to be added.
-  - `--global` (or `-g`) (optional): If provided, the repository alias should be added globally in `~/.agents/skills/`. This would be the default, but may be overriden by the `.agents/config.json` or `~/.agents/config.json`  setting for `installLocation`.
-  - `--project` (or `-p`) (optional): If provided, the repository alias should be added in the current project's `.agents/skills/` directory. If the project doens't already have a .agents/skills/ directory, it should be created. This would override the default global installation location and the `.agents/config.json` or `~/.agents/config.json` setting for `installLocation`.
-  - `--as={{REPOSITORY_ALIAS}}` (optional): If provided, the repository alias should be set to the specified value instead of deriving it from the repository name.
-- **Outputs**:
-  - On success, the command should print a confirmation message indicating that the repository alias has been added successfully, where it was added (globally or project-specific), and the alias name and what it is pointing to.
-  - On failure, the command should print an error message indicating what went wrong (e.g., invalid URL, unable to clone repository, etc.).
-
-1. Clone the repository to ~/.agents/tmp
-2. Read the skill.json file and read the `repository` field (String) 
-3. Add the value to the config.json file under `repositories` object with the key as the repository alias and value as the git URL.
-4. Clean up the ~/.agents/tmp directory
-
-### Variant with user provided alias
-- If the user provides the `--as={{REPOSITORY_ALIAS}}` parameter, use that value as the key in the `repositories` object instead of deriving it from the repository name.
-- **Command**: `superpowers-agent add-repository {{GIT_REPOSITORY_URL}} --as={{REPOSITORY_ALIAS}}`
-- Functionality: Same as above, but uses the provided alias.
-- Example Usage:
-  - Input: `superpowers-agent add-repository https://github.com/examples/skills-repo.git --as=@myskills`
-
-
-### Config.json Structure Example
-
-```json
-{
-  "installLocation": "global",
-  "repositories": {
-    "@examples": "https://github.com/examples/examples-multi-repo.git",
-    "@myskills": "https://github.com/myskills/skills-repo.git",
-  }
-}
-```
-
-### `superpowers-agent add` With Alias Updates
-- **Command**: `superpowers-agent add [options] {{REPOSITORY_ALIAS}} {{SKILLS_PATH}}`
-- **Functionality**: When a user runs this command with a GIT REPOSITORY, the agent should:
-- 1. Clone the repository into a temporary location in ~/.agents/tmp
-  1. Move to the directory path specified in the {{SKILLS_PATH}} within the cloned repository.
-  2. Read the skill.json file from the cloned repository to get skill data.
-  3. Read the `skills` array in skill.json (if present) to determine if there are multiple skills to install.
-  4. For each skill (or single skill if no `skills` array):
-     1. Read the individual skill.json file to get the skill's `name`.
-     2. Move the skill(s) to the appropriate skills directory:
-     3. - If `--global` is specified (or default), move to `~/.agents/skills/`
-        - If `--project` is specified, move to `.agents/skills/` in the current project directory.
-  5. Clean up the temporary cloned repository.
-  6. Return a success message listing the installed skills and their installation paths.
-- **Example Usage**:
-  - Input: 
-    
-    ```bash
-    superpowers-agent add-repository https://github.com/examples/skills-repo.git && \
-    superpowers-agent add @examples tests
-    ```
-
-  - Output: 
-  ```markdown
-    **Successfully installed skills:**
-    - Source: @examples
-      - Installed: tests/skill-one at ~/.agents/skills/tests/skill-five
-        Testing Skill Five
-  ```

package/.agents/prompts/current_prompt.md

@@ -1,8 +0,0 @@
-# Task 
-
-### Requirements
-
-- [ ] I want you to remove the code that causes the additions/updates to ~/.github/copilot-instructions.md when `superpowers-agent bootstrap` and `superpowers-agent update` commands are run.  The code is in `./.agents` folder, along with it's build tools, package.json, and src (`./.agents/src`).
-  - [ ] Instead I want an addition when the `superpowers-agent setup-skills` command is run, it should update the ./.github/copilot-instructions.md file of the project that it is run in when GitHub Copilot is detected following the same detection patterns already established in the `superpowers-agent setup-skills` command.
-  - [ ] The update to the ./.github/copilot-instructions.md file should be the same content that is currently being added to the ~/.github/copilot-instructions.md file, but it should be added to the ./.github/copilot-instructions.md file instead, and it should be added in a way that does not cause duplicates if the `superpowers-agent setup-skills` command is run multiple times in the same project where it makes a backup of the existing file and amends our connent to the end if the `<!-- SUPERPOWERS_-_INSTRUCTIONS_START -->` and `<!-- SUPERPOWERS_-_INSTRUCTIONS_END -->` markers ARE NOT already present, and if those markers are present, it should replace the content between those markers, making sure not to duplicate the markers themselves.
-  - [ ] Update the `.agents/package.json` file to `7.0.1` and tag the git release `7.0.1` and push the tag and main branch to origin when you are done with the updates.

package/.agents/prompts/post-migration-fixes-round-three.prompt.md

@@ -1,62 +0,0 @@
-# Post-Migration Fixes — Round Three
-
-You are working in an agentic coding environment with access to file system tools, web fetching, subagents, and skills.
-
-## Objective
-
-Fix the double `.git` suffix bug in the `add` command's repository cloning logic.
-
-**TARGET_VERSION: 8.2.2**
-
-## Problem
-
-When a repository URL already ends in `.git`, the clone step appends `.git` again, producing an invalid URL:
-```
-Input:  https://github.com/BlueAcornInc/skills.git
-Cloned: https://github.com/BlueAcornInc/skills.git.git  ← broken
-```
-
-This breaks `superpowers-agent add @baici` after `superpowers-agent add-repository` registers a `.git`-suffixed URL.
-
-## Phase 1 — Discover
-
-Before writing or modifying anything:
-
-1. Read `~/.agents/config.json` — understand how repository URLs and aliases are stored. Note if a previously registered repo with the bad URL is already present (this will interfere with testing).
-2. Read the `add-repository` command implementation — understand how it stores the repository URL.
-3. Read the `add` command implementation — trace the full path from alias resolution → URL construction → `git clone` invocation. Identify exactly where `.git` is appended.
-4. Check for any other commands that construct Git clone URLs — the same bug may exist elsewhere.
-
-## Phase 2 — Fix
-
-1. Fix the URL construction so it does not append `.git` if the URL already ends with `.git`.
-2. Apply the same fix to any other code paths identified in Phase 1 that construct clone URLs.
-3. Ensure URLs without `.git` suffix still work correctly (both forms are valid Git URLs).
-
-## Phase 3 — Verify
-
-1. Before testing, check `~/.agents/config.json` for any stale or malformed repository entries from previous failed attempts. Remove them if present so they don't interfere with validation.
-2. Confirm the clone URL is correct for inputs both with and without `.git` suffix.
-3. Search the codebase for any other instances of `.git` suffix appending that could produce the same bug.
-4. Set version to `8.2.2` in both `./package.json` and `.agents/package.json`.
-
-## Known Testing Gotcha
-
-`~/.agents/config.json` persists previously registered repositories. If a repo was added before this fix, the stored URL may already contain the double `.git`. Clear the relevant entry from `~/.agents/config.json` before re-testing `add-repository` and `add` commands.
-
-## Completion Criteria
-
-- Repository URLs ending in `.git` are not double-suffixed during clone
-- Repository URLs without `.git` continue to work correctly
-- No other code paths in the codebase have the same double-suffix bug
-- Both `./package.json` and `.agents/package.json` set to version `8.2.2`
-- No regressions in existing CLI functionality
-
-## Agent Instructions
-
-- Spawn parallel subagents where tasks are independent; each subagent owns a single concern
-  - Use Claude Sonnet 4.6 model for subagents
-- USE `leveraging-cli-tools` skill — use `rg`, `fd`, `jq`, `bat`, `ast-grep` over standard tools
-- Reason from facts only — read actual files before writing or modifying anything
-- Do not guess file contents, dependency structures, or platform behaviors — verify first
-- Concise output only; no padding

package/.agents/prompts/post-migration-fixes-round-two.prompt.md

@@ -1,37 +0,0 @@
-# Post-Migration Fixes: Update Checking, Version Source, Husky Hook, and Docs
-
-You are working in an agentic coding environment with access to file system tools, web fetching, subagents, and skills.
-
-## Objective
-
-TARGET_VERSION: **8.2.1**.
-
-FIX the following issues:
-
-I installed the new version and noticed some issues that need to be fixed:
-
-1. Version Checking is broken:
-  - `superpowers-agent version` returns `0.0.0`
-2. `superpowers-agent bootstrap` command is broken:
-  - Running `superpowers-agent bootstrap` is broken because most things look for `~/.agents/superpowers` directory which doesn't exist anymore since it's now installed as an npm package and not as a shell script that puts it in `~/.agents/superpowers`
-3. `superpowers-agent update` command is broken:
-  - Running `superpowers-agent update` is also broken for the same reason as above, it looks for the old directory structure that doesn't exist anymore. It should run the new update process `npm install -g @complexthings/superpowers-agent` instead to update the global npm package, after checking the npm registry for the latest version and comparing it to the current version to see if an update is actually needed before running the install command.
-4. `superpowers-agent check-updates` command is broken:
-  - It returns `0.0.0` for current version
-
-## Completion Criteria
-
-- Both `package.json` (`./package.json` & `.agents/package.json`) files set to version `<TARGET_VERSION>`
-- No regressions in existing CLI functionality
-
-## Agent Instructions
-
-- Spawn parallel subagents where tasks are independent; each subagent owns a single concern
-  - Use Claude Sonnet 4.6 model for subagents
-  - Phase 2 and Phase 3 are independent — run in parallel
-  - Phase 4 depends on Phase 1 discovery but is independent of Phases 2–3
-  - Phase 5 depends on Phases 2–4 completing (needs final change list)
-- USE `leveraging-cli-tools` skill — use `rg`, `fd`, `jq`, `bat`, `ast-grep` over standard tools
-- Reason from facts only — read actual files before writing or modifying anything
-- Do not guess file contents, dependency structures, or platform behaviors — verify first
-- Concise output only; no padding