@dreb/coding-agent 2.49.0 → 2.50.0

package/docs/mach6.md

@@ -30,7 +30,7 @@ Assess an existing GitHub issue or create a new one.
 /skill:mach6-issue add dark mode   # Create issue from description
 ```
 
-**Assess mode:** Launches parallel subagents to explore the codebase, then posts a structured assessment (summary, gaps, ambiguities, scope, risks) as an issue comment.
+**Assess mode:** Launches parallel Explore agents to retrieve bounded code/documentation evidence, then has the primary agent synthesize and post the assessment (summary, gaps, ambiguities, scope, risks) as an issue comment.
 
 **Create mode:** Drafts a structured issue with title, summary, acceptance criteria, and technical notes.
 
@@ -44,7 +44,7 @@ Explore the codebase, create an implementation plan, open a draft PR, and post t
 
 - Reads the issue and any existing assessment
 - Checks project conventions (AGENTS.md, CONTRIBUTING.md, etc.)
-- Launches parallel subagents to explore similar features, architecture, and integration points
+- Launches parallel Explore agents to locate related implementations, enumerate explicit flows/call sites, and quote bounded evidence; the primary agent owns architecture and planning
 - Creates a feature branch (`feature/issue-42-<slug>`) with an empty commit
 - Opens a draft PR linking to the issue
 - Posts the plan as a PR comment with `<!-- mach6-plan -->` marker
@@ -112,7 +112,7 @@ Pre-merge checks, version bump, docs update, merge, tag, and release.
 /skill:mach6-publish 53
 ```
 
-- Verifies CI passing, no merge conflicts, all findings addressed
+- Verifies CI passing with the blocking `watch_github_ci` tool (never `wait` or a polling loop), no merge conflicts, and all findings addressed
 - Runs pre-merge checklist (version bump, tests)
 - Applies version bump on the feature branch
 - Proactively reviews and updates ALL documentation affected by the PR's changes

package/docs/rpc.md

@@ -1112,7 +1112,7 @@ Response:
       },
       {
         "name": "Explore",
-        "description": "Codebase and web exploration — find files, search code, search the web, answer questions. Read-only."
+        "description": "Concrete evidence retrieval — locate files, symbols, documentation, call sites, and exact snippets. No implementation work."
       }
     ]
   }

package/docs/sdk.md

@@ -387,10 +387,10 @@ const { session } = await createAgentSession({ resourceLoader: loader });
 
 ```typescript
 import {
-  codingTools,   // read, bash, edit, write (subset — default is all 11)
+  codingTools,   // read, bash, edit, write (subset — default is all 13 standard tools)
   readOnlyTools, // read, grep, find, ls
   readTool, bashTool, editTool, writeTool,
-  grepTool, findTool, lsTool,
+  grepTool, findTool, lsTool, watchGithubCiTool,
 } from "@dreb/coding-agent";
 
 // Use built-in tool set
@@ -953,13 +953,13 @@ SettingsManager
 codingTools
 readOnlyTools
 readTool, bashTool, editTool, writeTool
-grepTool, findTool, lsTool
+grepTool, findTool, lsTool, watchGithubCiTool
 
 // Tool factories (for custom cwd)
 createCodingTools
 createReadOnlyTools
 createReadTool, createBashTool, createEditTool, createWriteTool
-createGrepTool, createFindTool, createLsTool
+createGrepTool, createFindTool, createLsTool, createWatchGithubCiTool
 
 // Types
 type CreateAgentSessionOptions

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/coding-agent",
-	"version": "2.49.0",
+	"version": "2.50.0",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"drebConfig": {

package/skills/mach6-implement/SKILL.md

@@ -133,13 +133,14 @@ tasks_update([
 
 #### If `ci` was specified:
 
+Use `watch_github_ci` with `pr: "<pr-number>"` so the tool blocks until the pull request's checks pass or fail. Do not use `wait`, sleep, or repeated polling commands for CI.
+
+If checks fail, use the returned check output to identify the failed run, then inspect it:
+
 ```bash
-gh pr checks <pr-number>
 gh run view <run-id> --log-failed
 ```
 
-**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.
-
 Read the failed CI logs and identify issues. Extract test failures, stack traces, error messages. If all checks pass, report this and stop.
 
 #### If finding numbers were specified:

package/skills/mach6-issue/SKILL.md

@@ -52,12 +52,12 @@ Update task: read → completed, explore → in_progress.
 
 ### Step 3: Explore the codebase
 
-Launch 2-3 Explore subagents in parallel targeting different aspects. Agent definitions specify their own model with a provider fallback list — defaults work across providers and are fine for most cases. Override only with good reason (e.g. a particularly complex issue warrants a stronger tier).
-- **Relevant code**: Find existing code related to the issue, trace implementation patterns
-- **Architecture**: Map relevant architecture layers, abstractions, data flow
-- **Prior work**: Check for related branches, PRs, or commits
+Launch 2-3 Explore subagents in parallel for concrete evidence retrieval. Agent definitions specify their own model with a provider fallback list — defaults work across providers and are fine for most cases. Override only with good reason (e.g. a large repository requires inspecting many files).
+- **Relevant code evidence**: Locate named related behavior and quote the exact implementation and test snippets
+- **Flow inventory**: Enumerate files, symbols, imports, calls, and registrations in an explicitly named existing flow without diagnosing it
+- **Prior-work evidence**: Locate related branches, PRs, commits, and documentation and report their exact references
 
-Each agent should return 5-10 key files. After agents complete, read all identified files.
+Do not ask Explore to determine the root cause, interpret ambiguous requirements, recommend an implementation, decide architecture, or assess the issue. Each agent should return 5-10 key files with bounded evidence. After agents complete, read all identified files and have the primary agent synthesize the current state, gaps, scope, and risks.
 
 Update task: explore → completed, assess → in_progress.
 
@@ -109,7 +109,7 @@ ls .github/ISSUE_TEMPLATE/ 2>/dev/null
 ```
 If templates exist, read them and select the most appropriate one.
 
-Explore the codebase if needed to understand the relevant area.
+If codebase context is needed, use Explore subagents only for bounded evidence such as locating named behavior, files, tests, call sites, or exact snippets. The primary agent must interpret that evidence and own the issue's requirements, proposed behavior, scope, and technical conclusions.
 
 ### Step 2: Draft the issue
 

package/skills/mach6-plan/SKILL.md

@@ -53,12 +53,12 @@ Extract planning-relevant guidance: project layers, testing expectations, coding
 
 ## Step 4: Explore the codebase
 
-Launch 2-3 Explore subagents in parallel. Agent definitions specify their own model with a provider fallback list — defaults work across providers and are fine for most cases. Override only with good reason (e.g. a particularly large or complex codebase warrants a stronger tier).
-- **Similar features**: Find existing code that solves related problems, trace implementation patterns
-- **Architecture**: Map relevant architecture layers, abstractions, data flow
-- **Integration points**: Identify where new code connects to existing systems
+Launch 2-3 Explore subagents in parallel for concrete evidence retrieval. Agent definitions specify their own model with a provider fallback list — defaults work across providers and are fine for most cases. Override only with good reason (e.g. a particularly large codebase requires inspecting many files).
+- **Existing feature evidence**: Locate named related features and quote the exact implementation and test snippets that establish their patterns
+- **Layer inventory**: Enumerate the files, symbols, imports, and calls in an explicitly named existing data flow without deciding the architecture
+- **Integration evidence**: Enumerate concrete call sites, registrations, configuration, and documentation for the relevant symbols
 
-Include project conventions in each agent's context. Each agent returns 5-10 key files. Read all identified files.
+Do not ask Explore to diagnose the problem, interpret ambiguous requirements, recommend an implementation, design the architecture, or produce the plan. Include project conventions in each agent's context. Each agent returns 5-10 key files with bounded evidence. Read all identified files, then have the primary agent synthesize the architecture, risks, and implementation plan.
 
 Update task: explore → completed, plan → in_progress.
 

package/skills/mach6-publish/SKILL.md

@@ -34,10 +34,9 @@ tasks_update([
 gh pr checkout <pr-number>
 git pull
 gh pr view <pr-number> --json mergeable,mergeStateStatus,statusCheckRollup,reviewDecision,comments,body
-gh pr checks <pr-number>
 ```
 
-**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.
+Use `watch_github_ci` with `pr: "<pr-number>"` to block until CI passes or fails. Do not use `wait`, sleep, or repeated polling commands for CI.
 
 Read ALL PR comments to understand the full history — plans, reviews, assessments, progress updates, and discussion.
 
@@ -90,7 +89,7 @@ Update task: checks → completed, version → in_progress.
    git push
    ```
 
-5. Wait for CI to pass on the version bump commit before proceeding to merge.
+5. Use `watch_github_ci` with `pr: "<pr-number>"` and proceed only after it reports that CI passed on the version bump commit.
 
 If the project doesn't use versioning, skip this step.
 
@@ -127,7 +126,7 @@ Proactively review and update ALL documentation affected by the PR's changes. Th
    git push
    ```
 
-5. Wait for CI to pass on the docs commit.
+5. Use `watch_github_ci` with `pr: "<pr-number>"` and proceed only after it reports that CI passed on the docs commit.
 
 If no documentation changes are needed (rare), skip this step.