@yemi33/minions 0.1.809 → 0.1.810
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 +2 -2
- package/package.json +1 -1
- package/playbooks/fix.md +8 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.1.
|
|
3
|
+
## 0.1.810 (2026-04-10)
|
|
4
4
|
|
|
5
5
|
### Features
|
|
6
6
|
- CC race condition fixes, doc-chat expand, settings save fix, metric rate
|
|
@@ -10,6 +10,7 @@
|
|
|
10
10
|
- cap review→fix cycles at evalMaxIterations (default 3)
|
|
11
11
|
|
|
12
12
|
### Fixes
|
|
13
|
+
- allow agents to explain rationale instead of blindly fixing review feedback
|
|
13
14
|
- don't URL-encode ADO branchName filter (refs/heads/ format expected raw)
|
|
14
15
|
- ADO build query filters by source branch (not all org builds)
|
|
15
16
|
- adoFetch supports method/body for PATCH requests (auto-complete)
|
|
@@ -29,7 +30,6 @@
|
|
|
29
30
|
- flush queued CC messages as single combined request
|
|
30
31
|
- human feedback fixes are never capped (only minion review→fix loop is)
|
|
31
32
|
- 5 bugs from comprehensive audit
|
|
32
|
-
- stale ADO build detection + merge conflict auto-fix for both platforms
|
|
33
33
|
|
|
34
34
|
## 0.1.782 (2026-04-10)
|
|
35
35
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.810",
|
|
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
|
@@ -29,7 +29,9 @@ Use subagents only for genuinely parallel, independent tasks. For sequential wor
|
|
|
29
29
|
|
|
30
30
|
1. You are already in the correct worktree on branch `{{pr_branch}}`. Do NOT create additional worktrees.
|
|
31
31
|
|
|
32
|
-
2.
|
|
32
|
+
2. For each issue listed above, use your judgment:
|
|
33
|
+
- **Fix it** if the feedback is valid and improves the code
|
|
34
|
+
- **Explain your rationale** if you believe the current approach is correct — reply on the review thread explaining why, with specific reasoning (e.g., performance, consistency with codebase patterns, intentional design choice). Do NOT silently ignore feedback — always respond.
|
|
33
35
|
|
|
34
36
|
3. Handle merge conflicts if any:
|
|
35
37
|
- If `git pull` or the PR shows conflicts, resolve them in the worktree
|
|
@@ -64,11 +66,11 @@ Do NOT remove the worktree — the engine handles cleanup automatically.
|
|
|
64
66
|
|
|
65
67
|
## Resolve Review Comments
|
|
66
68
|
|
|
67
|
-
After pushing,
|
|
68
|
-
- **
|
|
69
|
-
- **
|
|
70
|
-
|
|
71
|
-
|
|
69
|
+
After pushing, respond to each review comment/thread:
|
|
70
|
+
- **If you fixed it**: Reply confirming the fix, then resolve the thread
|
|
71
|
+
- **If you chose not to fix it**: Reply with your rationale explaining why the current approach is preferred — leave the thread open for the reviewer to decide
|
|
72
|
+
- **GitHub**: Reply to each review comment, resolve conversations you've fixed
|
|
73
|
+
- **ADO**: Reply to each thread, set status to `fixed` or `closed` for fixes; leave `active` for rationale replies
|
|
72
74
|
|
|
73
75
|
## When to Stop
|
|
74
76
|
|