@complexthings/superpowers-agent 8.2.2 → 8.3.0

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

@@ -1,90 +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
-
-Fix two issues introduced during the shell-to-npm migration, add a Husky pre-commit hook to keep versions synchronized, and update documentation to reflect today's changes. Target version: **8.2.0**.
-
-## Phase 1 — Discover
-
-Before writing or modifying anything:
-
-1. Read `git.js` — locate the `checkForUpdates` function and understand its current Git-based logic.
-2. Read `output.js` — locate the `getLocalVersion` function and understand how it currently resolves the version.
-3. Read `./package.json` and `.agents/package.json` — note current version values and any relevant fields.
-4. Check if `husky` is already a dependency or if any `.husky/` directory exists.
-5. Identify how the CLI is built (confirm `bun i && bun run build` in `.agents/`).
-6. Read `README.md` and `CHANGELOG.md` to understand their current structure and formatting conventions.
-
-## Phase 2 — Fix: Update Checking
-
-The `checkForUpdates` function in `git.js` currently checks the Git repo, which is unreliable post-migration.
-
-1. Create a new function that fetches the latest published version from the npm registry for the package (e.g., `https://registry.npmjs.org/@complexthings/superpowers-agent/latest`).
-2. Refactor `checkForUpdates` to use the npm registry function instead of the Git repo check.
-3. Compare the registry version against the locally installed version to determine if an update is available.
-
-## Phase 3 — Fix: Local Version Source
-
-The `getLocalVersion` function in `output.js` should read the version from `.agents/package.json` (the Bun-built CLI tool's package manifest).
-
-1. Update `getLocalVersion` to read and parse `.agents/package.json` for its `version` field.
-2. Remove or replace any previous version resolution logic that no longer applies.
-
-## Phase 4 — Add: Husky Pre-Commit Hook
-
-Add a `husky` pre-commit hook that enforces version parity between `./package.json` and `.agents/package.json`.
-
-1. Install `husky` as a dev dependency in the root. Initialize it (`npx husky init` or equivalent).
-2. Create a pre-commit hook script that does the following:
-   - Read `version` from `./package.json` and `.agents/package.json`.
-   - If versions match → proceed, no action needed.
-   - If versions differ:
-     1. Determine the HIGHEST version (semver comparison).
-     2. Update both `package.json` files to the highest version.
-     3. Run `npm i --package-lock-only` in the repo root to sync `package-lock.json`.
-     4. Run `bun i && bun run build` in `.agents/` to rebuild the CLI with the correct version.
-     5. Stage the changed files (`package.json`, `package-lock.json`, `.agents/package.json`, and build output) into the current commit.
-   - Allow the commit to proceed.
-
-## Phase 5 — Update Documentation
-
-1. Update `CHANGELOG.md` for version **8.2.0** dated **2026-03-16**, following the existing format. Document today's changes:
-   - Update checking now uses npm registry instead of Git repo
-   - `getLocalVersion` now reads from `.agents/package.json`
-   - Added Husky pre-commit hook to enforce version parity between root and `.agents/` package manifests
-2. Update `README.md` to reflect any install, usage, or behavior changes introduced by these fixes. Preserve existing structure — only modify or add sections relevant to today's changes.
-3. Ensure both `./package.json` and `.agents/package.json` have version set to `8.2.0`.
-
-## Phase 6 — Verify
-
-1. Confirm `checkForUpdates` no longer references Git-based version checking.
-2. Confirm `getLocalVersion` reads from `.agents/package.json`.
-3. Simulate a version mismatch between `./package.json` and `.agents/package.json` — run the pre-commit hook manually and verify it syncs versions, updates lockfiles, rebuilds, and stages changes.
-4. Confirm a matching-version scenario passes the hook with no modifications.
-5. Confirm both `package.json` files show version `8.2.0`.
-6. Confirm `CHANGELOG.md` has a `8.2.0` entry and `README.md` reflects current behavior.
-
-## Completion Criteria
-
-- `checkForUpdates` fetches latest version from npm registry, not Git
-- `getLocalVersion` reads version from `.agents/package.json`
-- Husky pre-commit hook installed and enforces version parity (highest wins)
-- Hook runs lockfile update and Bun rebuild when versions diverge, then stages all changes
-- Both `package.json` files set to version `8.2.0`
-- `CHANGELOG.md` updated with `8.2.0` entry for 2026-03-16
-- `README.md` updated to reflect current install/usage behavior
-- 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

package/.agents/prompts/refactor.prompt.md

@@ -1,33 +0,0 @@
-# Refactor: Shell Script Install → npm Package
-
-You are working in an agentic coding environment with access to file system tools, web fetching, subagents, and skills.
-
-## Objective
-
-I want to fix some issues I've noticed since the migration.
-
-Update checking:
-  - Right now it uses `checkForUpdates` in `git.js` which checks the Git Repo, but this is unreliable. Instead I'd like it to check the npm registry for the latest published version and compare it to the current version.
-  - This will require a new function to fetch the latest version from npm, and then update the existing `checkForUpdates` function to use that instead of the Git Repo.
-Get Local Version:
-  - The `getLocalVersion` in `output.js` function should read the version from the `package.json` file in `.agents/pacakge.json` for the bun built superpowers-agent cli tool.
-
-Additions I want:
-
-- Add `husky` pre-commit hook to the repo:
-  - It needs to check the `package.json` file in the root of the repo and the `package.json` file in the `.agents` directory to ensure that their versions match before allowing a commit. 
-    - IF they don't match
-      - THEN it needs to update the version to match in both, HIGHEST version wins
-      - THEN it needs to run `npm i --package-lock-only` in the root of the repo to ensure that the `package-lock.json` is updated with the new version for the root package as well.
-      - THEN it needs to run `bun i && bun run build` in the `.agents` directory to ensure that the built cli tool is updated with the new version as well.
-  - This will ensure that the versions are always in sync and that the built cli tool is always up to date with the version in the `package.json` files.
-  - Then add those changes to the commit and allow the commit to proceed.
-
-## 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