bigpowers 2.87.0 → 2.87.1

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.87.0",
+  "version": "2.87.1",
   "description": "81 skills — 73 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
   "keywords": [
     "pi-package"

package/CHANGELOG.md

@@ -1,3 +1,10 @@
+## [2.87.1](https://github.com/danielvm-git/bigpowers/compare/v2.87.0...v2.87.1) (2026-07-30)
+
+
+### Bug Fixes
+
+* **cli:** make bigpowers update self-update global package ([67f38f6](https://github.com/danielvm-git/bigpowers/commit/67f38f6e8dcf650732de01c87bf58aac0e20c52c))
+
 # [2.87.0](https://github.com/danielvm-git/bigpowers/compare/v2.86.8...v2.87.0) (2026-07-29)
 
 

package/README.md

@@ -43,15 +43,17 @@ After installing, ask your agent to run the `using-bigpowers` skill — it is th
 
 ```bash
 # Global install (no lifecycle scripts — npm v10+ safe)
-npm install -g bigpowers
+npm install -g bigpowers@latest
 bigpowers setup     # runs sync + install, links skills to your tools
 
-# Or one-shot with npx
-npx bigpowers setup
+# Or one-shot with npx (always fetches the newest release)
+npx bigpowers@latest setup
 ```
 
 Both commands sync skill artifacts and link them to Claude Code, Gemini CLI, and Cursor (see [Prerequisites](#-prerequisites)).
 
+> **Always pin `@latest`.** With bigpowers already installed globally, a bare `npx bigpowers setup` reuses the stale global binary and `npm update -g bigpowers` doesn't reliably cross to the newest release. `npm install -g bigpowers@latest` and `npx bigpowers@latest setup` force a registry fetch every time.
+
 ### Interactive Installer
 
 The `npx bigpowers setup` command launches an interactive menu where you can:
@@ -269,10 +271,11 @@ Or add manually to `.claude/settings.json`:
 **npm install:**
 
 ```bash
-npm update -g bigpowers
-bigpowers update   # re-sync and refresh symlinks
+bigpowers update   # fetches bigpowers@latest (global installs), then re-syncs + refreshes symlinks
 ```
 
+`bigpowers update` now runs `npm install -g bigpowers@latest` for you when bigpowers is installed globally, so running it alone is enough to reach the newest release. Prefer to do it by hand? `npm install -g bigpowers@latest && bigpowers update`. (Avoid `npm update -g bigpowers` — it does not reliably cross to `@latest`.)
+
 **git clone:**
 
 ```bash
@@ -301,9 +304,9 @@ bash scripts/install.sh --uninstall
 ### Reinstall
 
 ```bash
-npx bigpowers setup
+npx bigpowers@latest setup
 # or, if installed globally:
-bigpowers setup
+bigpowers update
 ```
 
 ---

package/bin/bigpowers.js

@@ -29,6 +29,43 @@ function run(cmd, cwd = ROOT) {
   }
 }
 
+// True when this copy runs from the global npm install (not a git clone or npx temp dir).
+function isGlobalInstall() {
+  try {
+    const globalRoot = execSync('npm root -g', { encoding: 'utf8' }).trim();
+    return globalRoot && ROOT.startsWith(globalRoot);
+  } catch {
+    return false;
+  }
+}
+
+// `bigpowers update` used to only re-sync the already-installed files, so it never fetched
+// a newer release. When we're the global install, pull the latest from npm first; the reinstall
+// overwrites ROOT in place, so the setup.js required afterwards is the freshly installed one.
+function selfUpdateGlobalPackage() {
+  if (!isGlobalInstall()) {
+    console.log('bigpowers: not a global npm install — skipping package self-update.');
+    console.log('  git clone → `git pull && npm run sync && bash scripts/install.sh`');
+    console.log('  one-shot  → `npx bigpowers@latest setup`');
+    return;
+  }
+  console.log('bigpowers: fetching the latest release from npm (npm install -g bigpowers@latest)...');
+  try {
+    execSync('npm install -g bigpowers@latest', { stdio: 'inherit' });
+  } catch {
+    console.error('bigpowers: `npm install -g bigpowers@latest` failed — re-syncing the installed version instead.');
+  }
+}
+
+// Best-effort registry check; silent on any failure so offline/slow networks never block a command.
+function latestPublishedVersion() {
+  try {
+    return execSync('npm view bigpowers version', { encoding: 'utf8', timeout: 4000 }).trim();
+  } catch {
+    return null;
+  }
+}
+
 const cmd = process.argv[2];
 
 if (cmd === 'setup' || cmd === 'install') {
@@ -39,7 +76,8 @@ if (cmd === 'setup' || cmd === 'install') {
 }
 
 if (cmd === 'update') {
-  // Delegate to interactive installer (same as setup)
+  // Pull the newest release first (global installs), then re-sync + refresh symlinks.
+  selfUpdateGlobalPackage();
   const setupScript = path.join(ROOT, 'bin', 'setup.js');
   require(setupScript);
   return;
@@ -51,6 +89,11 @@ if (cmd === 'status') {
       .filter(d => fs.lstatSync(path.join(os.homedir(), '.claude', 'skills', d)).isSymbolicLink())
       .length;
     console.log(`bigpowers v${pkg.version} — ${count} skills installed`);
+    const latest = latestPublishedVersion();
+    if (latest && latest !== pkg.version) {
+      console.log(`\n⬆️  A newer release is available: v${latest} (you have v${pkg.version}).`);
+      console.log('   Upgrade: npm install -g bigpowers@latest && bigpowers update');
+    }
   } else {
     console.log('bigpowers not installed. Run: bigpowers setup');
   }
@@ -63,8 +106,8 @@ bigpowers — agent skills for spec-driven, test-first development
 
 Commands:
   bigpowers setup    Install skills into ~/.claude/skills/
-  bigpowers update   Re-run sync and install (after npm update -g bigpowers)
-  bigpowers status   Show installed version and skill count
+  bigpowers update   Fetch the latest release (global installs) + re-sync and refresh symlinks
+  bigpowers status   Show installed version and skill count (warns if a newer release exists)
   bigpowers help     This message
 `);
   process.exit(0);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.87.0",
+  "version": "2.87.1",
   "description": "73 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
   "main": "index.js",
   "scripts": {