@dreb/coding-agent 2.11.0 → 2.11.1

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 (7) hide show
  1. package/package.json +1 -1
  2. package/skills/mach6-implement/SKILL.md +3 -0
  3. package/skills/mach6-issue/SKILL.md +10 -3
  4. package/skills/mach6-plan/SKILL.md +11 -4
  5. package/skills/mach6-publish/SKILL.md +7 -1
  6. package/skills/mach6-push/SKILL.md +6 -2
  7. package/skills/mach6-review/SKILL.md +15 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dreb/coding-agent",
3
- "version": "2.11.0",
3
+ "version": "2.11.1",
4
4
  "description": "Coding agent CLI with read, bash, edit, write tools and session management",
5
5
  "type": "module",
6
6
  "drebConfig": {
package/skills/mach6-implement/SKILL.md CHANGED
@@ -18,6 +18,7 @@ This skill has two modes:
18
18
  2. **No `#N` in comment bodies** — Use "finding 3", "item 3" etc. instead.
19
19
  3. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
20
20
  4. **Task tracking** — Use the `tasks_update` tool to show progress.
21
+ 5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
21
22
 
22
23
  ## Step 1: Parse input
23
24
 
@@ -121,6 +122,8 @@ gh pr checks <pr-number>
121
122
  gh run view <run-id> --log-failed
122
123
  ```
123
124
 
125
+ **Note:** `gh pr checks` returns exit code 8 while checks are still pending — this is expected, not a failure. Wait and re-run if needed.
126
+
124
127
  Read the failed CI logs and identify issues. Extract test failures, stack traces, error messages. If all checks pass, report this and stop.
125
128
 
126
129
  #### If finding numbers were specified:
package/skills/mach6-issue/SKILL.md CHANGED
@@ -16,6 +16,7 @@ argument-hint: "[issue-number | description]"
16
16
  4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets (.env, credentials, tokens, keys).
17
17
  5. **Task tracking** — Use the `tasks_update` tool to show progress through multi-step commands.
18
18
  6. **Project conventions** — Check for CLAUDE.md, AGENTS.md, .dreb/CONTEXT.md, and CONTRIBUTING.md before planning or implementing.
19
+ 7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
19
20
 
20
21
  ## Determine Mode
21
22
 
@@ -75,13 +76,16 @@ Present to the user:
75
76
  Post as an issue comment:
76
77
 
77
78
  ```bash
78
- gh issue comment <number> --body "<!-- mach6-assessment -->
79
+ cat > /tmp/gh-comment.md << 'MACH6_EOF'
80
+ <!-- mach6-assessment -->
79
81
  ## Issue Assessment
80
82
 
81
83
  <assessment content>
82
84
 
83
85
  ---
84
- *Automated assessment by mach6*"
86
+ *Automated assessment by mach6*
87
+ MACH6_EOF
88
+ gh issue comment <number> --body-file /tmp/gh-comment.md
85
89
  ```
86
90
 
87
91
  Update task: post → completed.
@@ -123,7 +127,10 @@ Present the draft to the user for approval.
123
127
  ### Step 3: Create the issue
124
128
 
125
129
  ```bash
126
- gh issue create --title "<title>" --body "<body>" [--label "<labels>"]
130
+ cat > /tmp/gh-body.md << 'MACH6_EOF'
131
+ <body>
132
+ MACH6_EOF
133
+ gh issue create --title "<title>" --body-file /tmp/gh-body.md [--label "<labels>"]
127
134
  ```
128
135
 
129
136
  Report the issue number and URL. Suggest next step: `/skill:mach6-plan <number>`
package/skills/mach6-plan/SKILL.md CHANGED
@@ -18,6 +18,7 @@ This command is strictly for **planning**. Do NOT implement any code changes —
18
18
  4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
19
19
  5. **Task tracking** — Use the `tasks_update` tool to show progress through multi-step commands.
20
20
  6. **Project conventions** — Check for CLAUDE.md, AGENTS.md, .dreb/CONTEXT.md, and CONTRIBUTING.md before planning.
21
+ 7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
21
22
 
22
23
  ## Step 1: Set up task tracking
23
24
 
@@ -97,11 +98,14 @@ git commit --allow-empty -m "chore: open PR for issue <N>"
97
98
  git push -u origin feature/issue-<N>-<slug>
98
99
 
99
100
  # Open draft PR
100
- gh pr create --draft --title "<title>" --body "Closes #<N>
101
+ cat > /tmp/gh-body.md << 'MACH6_EOF'
102
+ Closes #<N>
101
103
 
102
104
  <brief description>
103
105
 
104
- Implementation plan posted as a comment below."
106
+ Implementation plan posted as a comment below.
107
+ MACH6_EOF
108
+ gh pr create --draft --title "<title>" --body-file /tmp/gh-body.md
105
109
  ```
106
110
 
107
111
  Update task: branch → completed, post → in_progress.
@@ -109,13 +113,16 @@ Update task: branch → completed, post → in_progress.
109
113
  ## Step 7: Post plan to PR
110
114
 
111
115
  ```bash
112
- gh pr comment <pr-number> --body "<!-- mach6-plan -->
116
+ cat > /tmp/gh-comment.md << 'MACH6_EOF'
117
+ <!-- mach6-plan -->
113
118
  ## Implementation Plan
114
119
 
115
120
  <full plan content>
116
121
 
117
122
  ---
118
- *Plan created by mach6*"
123
+ *Plan created by mach6*
124
+ MACH6_EOF
125
+ gh pr comment <pr-number> --body-file /tmp/gh-comment.md
119
126
  ```
120
127
 
121
128
  Update task: post → completed.
package/skills/mach6-publish/SKILL.md CHANGED
@@ -14,6 +14,7 @@ argument-hint: "<pr-number>"
14
14
  2. **No `#N` in comment bodies** — Use "finding 3", "item 3" etc. instead.
15
15
  3. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
16
16
  4. **Task tracking** — Use the `tasks_update` tool to show progress.
17
+ 5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
17
18
 
18
19
  ## Step 1: Set up task tracking
19
20
 
@@ -36,6 +37,8 @@ gh pr view <pr-number> --json mergeable,mergeStateStatus,statusCheckRollup,revie
36
37
  gh pr checks <pr-number>
37
38
  ```
38
39
 
40
+ **Note:** `gh pr checks` returns exit code 8 while checks are still pending — this is expected, not a failure. Wait and re-run if needed.
41
+
39
42
  Read ALL PR comments to understand the full history — plans, reviews, assessments, progress updates, and discussion.
40
43
 
41
44
  Verify:
@@ -178,7 +181,10 @@ git push --tags
178
181
 
179
182
  3. Present draft to user for approval, then create:
180
183
  ```bash
181
- gh release create v<version> --title "v<version>" --notes "<release-notes>"
184
+ cat > /tmp/gh-release-notes.md << 'MACH6_EOF'
185
+ <release-notes>
186
+ MACH6_EOF
187
+ gh release create v<version> --title "v<version>" --notes-file /tmp/gh-release-notes.md
182
188
  ```
183
189
 
184
190
  Update task: release → completed.
package/skills/mach6-push/SKILL.md CHANGED
@@ -15,6 +15,7 @@ argument-hint: "[commit message]"
15
15
  3. **No `#N` in comment bodies** — Use "finding 3", "item 3", "stage 2" etc. instead.
16
16
  4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets (.env, credentials, tokens, keys).
17
17
  5. **Task tracking** — Use the `tasks_update` tool to show progress.
18
+ 6. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
18
19
 
19
20
  ## Step 1: Set up task tracking
20
21
 
@@ -80,7 +81,8 @@ If session context points to an issue but a PR also exists on the current branch
80
81
 
81
82
  Post a progress comment:
82
83
  ```bash
83
- gh pr comment <number> --body "<!-- mach6-progress -->
84
+ cat > /tmp/gh-comment.md << 'MACH6_EOF'
85
+ <!-- mach6-progress -->
84
86
  ## Progress Update
85
87
 
86
88
  <summary of changes in this batch>
@@ -88,7 +90,9 @@ gh pr comment <number> --body "<!-- mach6-progress -->
88
90
  **Commit:** \`<hash>\`
89
91
 
90
92
  ---
91
- *Progress tracked by mach6*"
93
+ *Progress tracked by mach6*
94
+ MACH6_EOF
95
+ gh pr comment <number> --body-file /tmp/gh-comment.md
92
96
  ```
93
97
 
94
98
  Update task: comment → completed.
package/skills/mach6-review/SKILL.md CHANGED
@@ -14,6 +14,7 @@ argument-hint: "<pr-number> [code|errors|tests|completeness|simplify]"
14
14
  2. **HTML markers** — Use `<!-- mach6-review -->` and `<!-- mach6-assessment -->` as the first line of comment bodies.
15
15
  3. **No `#N` in comment bodies** — Use "finding 3", "item 3", "stage 2" etc. instead.
16
16
  4. **Task tracking** — Use the `tasks_update` tool to show progress.
17
+ 5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks.
17
18
 
18
19
  **Important: Do NOT fix any issues in this session. Fixes happen via `/skill:mach6-implement`.**
19
20
 
@@ -95,7 +96,8 @@ Update task: review → completed, post-review → in_progress.
95
96
  Compile all findings from all agents into a single structured comment:
96
97
 
97
98
  ```bash
98
- gh pr comment <pr-number> --body "<!-- mach6-review -->
99
+ cat > /tmp/gh-comment.md << 'MACH6_EOF'
100
+ <!-- mach6-review -->
99
101
  ## Code Review
100
102
 
101
103
  ### Critical
@@ -113,7 +115,9 @@ gh pr comment <pr-number> --body "<!-- mach6-review -->
113
115
  **Agents run:** <list of agents>
114
116
 
115
117
  ---
116
- *Reviewed by mach6*"
118
+ *Reviewed by mach6*
119
+ MACH6_EOF
120
+ gh pr comment <pr-number> --body-file /tmp/gh-comment.md
117
121
  ```
118
122
 
119
123
  Save the review comment URL:
@@ -152,7 +156,8 @@ Update task: assess → completed, post-assess → in_progress.
152
156
  ## Step 7: Post assessment
153
157
 
154
158
  ```bash
155
- gh pr comment <pr-number> --body "<!-- mach6-assessment -->
159
+ cat > /tmp/gh-comment.md << 'MACH6_EOF'
160
+ <!-- mach6-assessment -->
156
161
  ## Review Assessment
157
162
 
158
163
  <link to review comment>
@@ -168,7 +173,9 @@ gh pr comment <pr-number> --body "<!-- mach6-assessment -->
168
173
  <numbered list of what to fix, ordered by priority>
169
174
 
170
175
  ---
171
- *Assessment by mach6*"
176
+ *Assessment by mach6*
177
+ MACH6_EOF
178
+ gh pr comment <pr-number> --body-file /tmp/gh-comment.md
172
179
  ```
173
180
 
174
181
  Update task: post-assess → completed, summary → in_progress.
@@ -182,7 +189,10 @@ Present to the user:
182
189
 
183
190
  If any findings were classified as **deferred**, ask the user if they want to create issues for them:
184
191
  ```bash
185
- gh issue create --title "<title>" --body "<body referencing PR and finding>"
192
+ cat > /tmp/gh-body.md << 'MACH6_EOF'
193
+ <body referencing PR and finding>
194
+ MACH6_EOF
195
+ gh issue create --title "<title>" --body-file /tmp/gh-body.md
186
196
  ```
187
197
 
188
198
  Update task: summary → completed.