@yemi33/minions 0.1.248 → 0.1.250
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 +8 -0
- package/package.json +1 -1
- package/playbooks/fix.md +9 -0
- package/playbooks/implement.md +13 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.250 (2026-04-03)
|
|
4
|
+
|
|
5
|
+
### Features
|
|
6
|
+
- mandatory test validation before PR creation in implement and fix playbooks
|
|
7
|
+
|
|
8
|
+
### Fixes
|
|
9
|
+
- don't hardcode npm test — agents must read project conventions
|
|
10
|
+
|
|
3
11
|
## 0.1.248 (2026-04-03)
|
|
4
12
|
|
|
5
13
|
### Fixes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.250",
|
|
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"
|
package/playbooks/fix.md
CHANGED
|
@@ -43,6 +43,15 @@ If you encounter merge conflicts (e.g., during `git pull` or when the PR shows c
|
|
|
43
43
|
- content: Explain what was fixed, reference each review finding
|
|
44
44
|
- Sign: `Fixed by Minions ({{agent_name}} — {{agent_role}})`
|
|
45
45
|
|
|
46
|
+
## Test Validation (MANDATORY before pushing)
|
|
47
|
+
|
|
48
|
+
Before pushing your fix, run the project's test suite:
|
|
49
|
+
|
|
50
|
+
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.
|
|
51
|
+
2. Run the full test suite using whatever command the project specifies
|
|
52
|
+
3. If any tests fail due to your changes, fix them before pushing
|
|
53
|
+
4. Do NOT push code that breaks existing tests
|
|
54
|
+
|
|
46
55
|
## Signal Completion
|
|
47
56
|
|
|
48
57
|
**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
|
package/playbooks/implement.md
CHANGED
|
@@ -68,3 +68,16 @@ After building, verify the build succeeded. If the build fails:
|
|
|
68
68
|
2. Fix the issue
|
|
69
69
|
3. Re-run the build
|
|
70
70
|
4. If it fails 3 times, report the build errors in your findings file and stop
|
|
71
|
+
|
|
72
|
+
## Test Validation (MANDATORY before PR)
|
|
73
|
+
|
|
74
|
+
Before creating a PR, you MUST run the project's test suite and ensure all existing tests pass:
|
|
75
|
+
|
|
76
|
+
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.
|
|
77
|
+
2. Run the full test suite using whatever command the project specifies
|
|
78
|
+
3. If any tests fail:
|
|
79
|
+
- Determine if YOUR changes caused the failure (compare with the failing test's assertions)
|
|
80
|
+
- Fix any regressions you introduced
|
|
81
|
+
- Re-run tests until all pass
|
|
82
|
+
4. If tests were already failing before your changes (pre-existing failures), note them in the PR description but do NOT block on them
|
|
83
|
+
5. Do NOT create a PR with failing tests that you introduced
|