Repository navigation
Closed as not planned
Closed as not planned
Copy link
Labels
dev-lead:hands-offExclude from dev-lead agent automationExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)Initiative driver must not release this issue (human hold)
Description
Story
As a platform owner,
I want enable a starter MCP server on a single downstream repo, run real reviews, and record a short before/after note on review quality and latency,
so that an evidence-based go/no-go before any broader rollout.
Acceptance Criteria
- One downstream repo is selected and MCP review enabled there using the story-1 knob plus a starter server (GitHub MCP secret scanning per the MCP-Powered CI Review Enhancement — Standard #650 weekly-update recommendation, or Context7 as the no-auth fallback).
- A small sample of PRs is reviewed with MCP on, and results are captured (framework-aware findings, deprecated-API / secret / dependency catches that surfaced).
- The latency delta versus MCP-off is recorded (the idea claims marginal/ms-range; verify against real runs).
- A short pilot note records findings and a rollout recommendation; broader rollout remains a separate, explicit human decision.
Tasks / Subtasks
- Select the downstream repo and starter server; confirm prerequisites (the security-first gate has landed). (AC: test issue from agent #1)
- Enable MCP review on that repo via the committed-config/knob convention from story 3. (AC: test issue from agent #1)
- Run a sample of PR reviews with MCP on and capture qualitative findings. (AC: Go-live improvements for PR review agent #2)
- Measure and record latency delta vs MCP-off. (AC: Add @claude delegation, auto-merge, and rebase handling #3)
- Write the pilot note + rollout recommendation; flag rollout as a separate human decision. (AC: Optimize review: small-PR and incremental fast paths #4)
Dev Notes
- Depends on plumbing (story 1), graceful degradation (story 2), the enablement path (story 3), and the per-stack docs/server guidance (story 4).
- PREREQUISITE per MCP-Powered CI Review Enhancement — Standard #650: in-flight security-hardening (action allowlisting, input sanitization) must land FIRST. That work is not tracked as a repo issue in the planning context (referenced_issues is empty), so it is an external gate — see open_questions — not a blocked_by edge. Do not start the pilot before it lands.
- Starter-server choice: the 2026-06-13 weekly update revises the recommended first step to GitHub MCP secret/dependency scanning (GA/preview, no extra auth, security-aligned) over Context7; Context7 remains the zero-auth fallback.
- Review-quality/latency signal already exists in this repo via scripts/pr_review_health.sh and the daily health workflow — reuse it rather than building a new measurement harness.
- Operational/human-gated: choosing the repo, enabling MCP on an external repo, and the rollout decision are human calls — hence hands_off.
Project Structure Notes
Primarily operational; any artifact is the pilot note (in the story-4 doc or an issue comment). Reuses existing review-health tooling for measurement.
References
- discussion MCP-Powered CI Review Enhancement — Standard #650 (Next Steps 4 + weekly-update revised sequencing)
- scripts/pr_review_health.sh (existing review-quality signal)
- .github/workflows/daily-pr-review-health.yml
Likely target surface
docs/initiatives/scripts/pr_review_health.sh
Story prepared by the BMAD Scrum Master (Bob) for epic #676. Status: ready-for-dev.
Metadata
Metadata
Assignees
Labels
dev-lead:hands-offExclude from dev-lead agent automationExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)Initiative driver must not release this issue (human hold)
Activity
pilot(mcp): enable GitHub MCP secret-scanning for .github-private rev…
pilot(mcp): scan PR diffs for secrets via run_secret_scanning (#681)
pilot(mcp): scan PR diffs for secrets via run_secret_scanning (#783)
pilot(mcp): scan for secrets on the triage-approved path too (#786)
pilot(mcp): thread REVIEW_MCP_ALLOWED_TOOLS into the review job env (#…
don-petry commentedon Jun 20, 2026
Pilot note — closing (outcome: tool reachable, starter server blocked by plan)
This records the Phase-2 pilot result and the go/no-go, per AC #4.
What was validated ✅
REVIEW_MCP_ALLOWED_TOOLS=mcp__github__*is confirmed in the live job env, the GitHub MCP server connects, andrun_secret_scanningis reachable and permitted — the earlier "not permitted" failure is gone. The pipeline (story 1) and graceful-degradation (story 2) paths behave as designed: on the tool being unavailable, the review still completes and cleanly annotates the gap.claudeengine —COPILOT_API_MODEL: unbound variable#774 viadry_run=trueforce-review runs.What blocked the starter server ⛔
run_secret_scanning, per the 2026-06-13 weekly-update revised sequencing) — is a content-scanning API that gates on the repo'sadvanced_securityflag (full GitHub Advanced Security).advanced_securityflag is not available on the current plan for this private repo.Repository does not have GitHub Advanced Security enabled— identically from two independent tokens (the session token and the workflow'sdonpetry-bottoken), confirming this is a repo/plan feature-flag gate, not an auth or call-shape problem. The call type and params are correct; there is no alternate GitHub API for this capability.Latency (AC #3)
Interim secret coverage
Secret scan (gitleaks)CI check covers secrets today, plan-independent — so closing this pilot does not leave a coverage gap.Recommendation / go-no-go
advanced_securitypurchase solely for the pilot.Closing as not planned for the original starter; the capability work continues under the follow-up.
Refs: epic #676, #809 (env-mapping fix), discussion #650 (revised sequencing), PR #774 (pilot subject).
Generated by Claude Code
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845)
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…
chore(lsp-pilot): retire the LSP pilot after Shell NO-GO (#839, #845) (…