@yemi33/minions 0.1.624 → 0.1.625

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.
package/CHANGELOG.md CHANGED
@@ -1,8 +1,9 @@
1
1
  # Changelog
2
2
 
3
- ## 0.1.624 (2026-04-08)
3
+ ## 0.1.625 (2026-04-08)
4
4
 
5
5
  ### Fixes
6
+ - reorder implement-shared playbook — build & test before push
6
7
  - reorder implement playbook — build & test before push
7
8
 
8
9
  ## 0.1.623 (2026-04-08)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yemi33/minions",
3
- "version": "0.1.624",
3
+ "version": "0.1.625",
4
4
  "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
5
5
  "bin": {
6
6
  "minions": "bin/minions.js"
@@ -31,13 +31,7 @@ Check what's already on this branch:
31
31
  git log --oneline {{main_branch}}..HEAD
32
32
  ```
33
33
 
34
- Do ALL work in the worktree. When done:
35
-
36
- ```bash
37
- git add <specific files>
38
- git commit -m "{{commit_message}}"
39
- git push origin {{branch_name}}
40
- ```
34
+ Do ALL work in the worktree.
41
35
 
42
36
  **Do NOT:**
43
37
  - Create a new branch — use `{{branch_name}}`
@@ -60,17 +54,27 @@ Use subagents only for genuinely parallel, independent tasks. For sequential wor
60
54
  3. Follow existing patterns exactly — check `CLAUDE.md` for conventions
61
55
  4. Build on existing work — don't duplicate or conflict with prior commits
62
56
 
63
- ## Build and Verify
57
+ ## Build & Test (MANDATORY before pushing)
64
58
 
65
- After implementation:
66
- 1. Build the project using the repo's build system (check CLAUDE.md, package.json, README)
59
+ After implementation, verify everything works:
60
+
61
+ 1. **Build** the project using its build system (check CLAUDE.md, package.json, README, Makefile)
67
62
  2. Verify the build succeeds with your changes AND all prior commits on this branch
68
- 3. If the build fails:
69
- - Read the error output carefully
70
- - Fix the issue (including issues from prior commits if needed)
71
- - Re-run the build
72
- - If it fails 3 times, report the build errors in your findings and stop
63
+ 3. **Run the full test suite** — fix any regressions you introduced
64
+ 4. **Run any other checks** the repo defines (linting, type checking, formatting)
65
+ 5. If the build fails 3 times, report the errors in your findings and stop
66
+ 6. Do NOT push code with a broken build or failing tests that you introduced
67
+
68
+ ## Push
69
+
70
+ Only after build and tests pass:
71
+
72
+ ```bash
73
+ git add <specific files>
74
+ git commit -m "{{commit_message}}"
75
+ git push origin {{branch_name}}
76
+ ```
73
77
 
74
78
  ## When to Stop
75
79
 
76
- Your task is complete once you have committed and pushed your changes to the shared branch. Do NOT create a PR — the engine creates one when all plan items are done. Stop after pushing.
80
+ Your task is complete once you have: (1) confirmed build and tests pass, and (2) pushed to the shared branch. Do NOT create a PR — the engine creates one when all plan items are done. Stop after pushing.