bigpowers 2.85.1 → 2.85.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (18) hide show
  1. package/.agents/skills/assess-impact/SKILL.md +1 -1
  2. package/.codebuddy/skills/assess-impact/SKILL.md +1 -1
  3. package/.codex/skills/assess-impact/SKILL.md +1 -1
  4. package/.hermes/skills/assess-impact/SKILL.md +1 -1
  5. package/.kilocode/rules/assess-impact.md +1 -1
  6. package/.mimocode/skills/assess-impact/SKILL.md +1 -1
  7. package/.pi/package.json +1 -1
  8. package/.pi/prompts/assess-impact.md +1 -1
  9. package/.pi/skills/assess-impact/SKILL.md +1 -1
  10. package/.trae/skills/assess-impact/SKILL.md +1 -1
  11. package/.windsurf/rules/assess-impact.md +1 -1
  12. package/.zcode/skills/assess-impact/SKILL.md +1 -1
  13. package/CHANGELOG.md +7 -0
  14. package/package.json +1 -1
  15. package/scripts/lib/__pycache__/link_utils.cpython-312.pyc +0 -0
  16. package/scripts/lib/__pycache__/srp_engine_links.cpython-312.pyc +0 -0
  17. package/skills/assess-impact/SKILL.md +1 -1
  18. package/skills-lock.json +1 -1
package/.agents/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.codebuddy/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.codex/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.hermes/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.kilocode/rules/assess-impact.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.mimocode/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.pi/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.85.1",
3
+ "version": "2.85.2",
4
4
  "description": "80 skills — 73 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
5
5
  "keywords": [
6
6
  "pi-package"
package/.pi/prompts/assess-impact.md CHANGED
@@ -33,7 +33,7 @@ git log --oneline -10 -- [file-path]
33
33
 
34
34
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
35
35
 
36
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
36
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
37
37
 
38
38
  ### 4. List test coverage
39
39
 
package/.pi/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.trae/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.windsurf/rules/assess-impact.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/.zcode/skills/assess-impact/SKILL.md CHANGED
@@ -34,7 +34,7 @@ git log --oneline -10 -- [file-path]
34
34
 
35
35
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
36
36
 
37
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
37
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
38
38
 
39
39
  ### 4. List test coverage
40
40
 
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ ## [2.85.2](https://github.com/danielvm-git/bigpowers/compare/v2.85.1...v2.85.2) (2026-07-25)
2
+
3
+
4
+ ### Bug Fixes
5
+
6
+ * **verify:** fix assess-impact verify line case sensitivity ([3a51a28](https://github.com/danielvm-git/bigpowers/commit/3a51a28aaad1dfd19bb256d8e10e09da6514be76))
7
+
1
8
  ## [2.85.1](https://github.com/danielvm-git/bigpowers/compare/v2.85.0...v2.85.1) (2026-07-25)
2
9
 
3
10
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.85.1",
3
+ "version": "2.85.2",
4
4
  "description": "73 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/skills/assess-impact/SKILL.md CHANGED
@@ -35,7 +35,7 @@ git log --oneline -10 -- [file-path]
35
35
 
36
36
  Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
37
37
 
38
- → verify: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
38
+ → verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
39
39
 
40
40
  ### 4. List test coverage
41
41
 
package/skills-lock.json CHANGED
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "assess-impact": {
10
10
  "description": "Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks \"what does this break?\".",
11
- "sha256": "5a443f358b8a2369",
11
+ "sha256": "4168a9484c4e7d30",
12
12
  "path": "skills/assess-impactSKILL.md"
13
13
  },
14
14
  "audit-code": {