@yemi33/minions 0.1.623 → 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 +6 -0
- package/package.json +1 -1
- package/playbooks/implement-shared.md +20 -16
- package/playbooks/implement.md +22 -29
package/CHANGELOG.md
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
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.
|
|
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
|
|
57
|
+
## Build & Test (MANDATORY before pushing)
|
|
64
58
|
|
|
65
|
-
After implementation:
|
|
66
|
-
|
|
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.
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
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
|
|
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.
|
package/playbooks/implement.md
CHANGED
|
@@ -47,8 +47,27 @@ Use subagents only for genuinely parallel, independent tasks (e.g., editing file
|
|
|
47
47
|
## Git Workflow
|
|
48
48
|
|
|
49
49
|
You are already running in a git worktree on branch `{{branch_name}}`. Do NOT create additional worktrees — the engine pre-created one for you.
|
|
50
|
+
Do NOT remove the worktree — the engine handles cleanup automatically.
|
|
51
|
+
|
|
52
|
+
## Build & Test (MANDATORY before pushing)
|
|
50
53
|
|
|
51
|
-
|
|
54
|
+
After implementation, verify everything works before pushing:
|
|
55
|
+
|
|
56
|
+
1. **Build** the project using its build system (check CLAUDE.md, package.json, README, Makefile). If the build fails:
|
|
57
|
+
- Read the error, fix the issue, re-build
|
|
58
|
+
- If it fails 3 times, report the errors in your findings and stop
|
|
59
|
+
2. **Run the full test suite** using whatever command the project specifies (check CLAUDE.md, agent.md, README, or package.json scripts).
|
|
60
|
+
3. If any tests fail:
|
|
61
|
+
- Determine if YOUR changes caused the failure
|
|
62
|
+
- Fix any regressions you introduced
|
|
63
|
+
- Re-run tests until all pass
|
|
64
|
+
4. If tests were already failing before your changes (pre-existing), note them in the PR description but do NOT block on them
|
|
65
|
+
5. **Run any other checks** the repo defines (linting, type checking, formatting) — read project docs for the full list
|
|
66
|
+
6. Do NOT push code with failing tests or a broken build that you introduced
|
|
67
|
+
|
|
68
|
+
## Push & Create PR
|
|
69
|
+
|
|
70
|
+
Only after build and tests pass:
|
|
52
71
|
|
|
53
72
|
```bash
|
|
54
73
|
git add <specific files>
|
|
@@ -56,36 +75,10 @@ git commit -m "{{commit_message}}"
|
|
|
56
75
|
git push -u origin {{branch_name}}
|
|
57
76
|
```
|
|
58
77
|
|
|
59
|
-
Do NOT remove the worktree — the engine handles cleanup automatically.
|
|
60
|
-
|
|
61
78
|
{{pr_section}}
|
|
62
79
|
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
After implementation:
|
|
66
|
-
1. Build the project using the repo's build system (check CLAUDE.md, package.json, README)
|
|
67
|
-
2. Start if applicable
|
|
68
|
-
3. Include the browser URL and run instructions in the PR description
|
|
69
|
-
|
|
70
|
-
After building, verify the build succeeded. If the build fails:
|
|
71
|
-
1. Read the error output carefully
|
|
72
|
-
2. Fix the issue
|
|
73
|
-
3. Re-run the build
|
|
74
|
-
4. If it fails 3 times, report the build errors in your findings file and stop
|
|
75
|
-
|
|
76
|
-
## Test Validation (MANDATORY before PR)
|
|
77
|
-
|
|
78
|
-
Before creating a PR, run the project's test suite and ensure all existing tests pass:
|
|
79
|
-
|
|
80
|
-
1. Find the test command by reading the project's own documentation — check CLAUDE.md, agent.md, README, or package.json scripts in the project root. Every project defines its own conventions.
|
|
81
|
-
2. Run the full test suite using whatever command the project specifies
|
|
82
|
-
3. If any tests fail:
|
|
83
|
-
- Determine if YOUR changes caused the failure (compare with the failing test's assertions)
|
|
84
|
-
- Fix any regressions you introduced
|
|
85
|
-
- Re-run tests until all pass
|
|
86
|
-
4. If tests were already failing before your changes (pre-existing failures), note them in the PR description but do NOT block on them
|
|
87
|
-
5. Do NOT create a PR with failing tests that you introduced
|
|
80
|
+
Include build/test status and run instructions in the PR description. If the project has a runnable app, include the localhost URL.
|
|
88
81
|
|
|
89
82
|
## When to Stop
|
|
90
83
|
|
|
91
|
-
Your task is complete once you have: (1)
|
|
84
|
+
Your task is complete once you have: (1) confirmed build and tests pass, (2) pushed your branch, and (3) created the PR. Do NOT continue exploring, refactoring, or adding features beyond the task description. Stop immediately.
|