fix(52): replace stale MCP issue refs and refresh Wave 2 execution#494
Conversation
📝 WalkthroughWalkthroughThis PR updates the project execution plan to version 1.1.0 with revised Wave 2 batching structure, and systematically migrates deprecated MCP tool references (create_issue → issue_write, get_issue → issue_read) across prompt and agent configuration files. Changes are documented in CHANGELOG.md. ChangesIssue
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
github-actions
Bot
added
area:documentation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c71ea31836
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "issue_write", | ||
| "search_issues", | ||
| "update_issue", |
There was a problem hiding this comment.
This prompt still allow-lists update_issue even though the change migrates issue creation to the consolidated MCP tool. I checked the current GitHub MCP issue tool list, where updates are handled by issue_write with method: 'update', and update_issue is no longer listed; in hosts that validate prompt frontmatter tool names exactly, the update-existing path can fail to load or become unavailable. The same stale allow-list entry appears in the other two issue-creation prompts.
Useful? React with 👍 / 👎.
| "issue_read", | ||
| "get_issue_comments", |
There was a problem hiding this comment.
This swaps get_issue to issue_read but leaves get_issue_comments in the prompt allow-list. The current GitHub MCP issue tools consolidate comment reads into issue_read with the get_comments method, so environments that exact-check prompt tool names can reject this prompt or leave the comment-count workflow without the declared read tool.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/projects/active/next-issues-execution-plan-2026-05-27.md:
- Line 15: Add a single top-level H1 above the existing "## Next Issues
Execution Plan (2026-05-28)" heading so the file contains one H1 and subsequent
headings are sequential; specifically insert a "# Next Issues Execution Plan
(2026-05-28)" (or a brief equivalent H1 title) immediately before the current
"## Next Issues Execution Plan (2026-05-28)" line to satisfy the "*.md: Use one
H1 per file and keep heading levels sequential" guideline.
In `@agents/mode-prd.agent.md`:
- Around line 14-16: Add the new tool names "issue_write" and "issue_read" to
the validator allowlist by updating the validTools array in
scripts/validation/validate-agents.js so the agent config entries
("issue_write", "update_issue", "issue_read") are recognized; locate the
validTools symbol in that file and append these two strings to the list
(preserving formatting and any existing sorting conventions) so validation no
longer flags them as Unknown tool.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 12809a52-d541-48f6-b25c-21136adbb058
📒 Files selected for processing (7)
.github/projects/active/next-issues-execution-plan-2026-05-27.md.github/prompts/create-github-issue-feature-from-specification.prompt.md.github/prompts/create-github-issues-feature-from-implementation-plan.prompt.md.github/prompts/create-github-issues-for-unmet-specification-requirements.prompt.md.github/prompts/my-issues.prompt.mdCHANGELOG.mdagents/mode-prd.agent.md
| --- | ||
|
|
||
| ## Next Issues Execution Plan (2026-05-27) | ||
| ## Next Issues Execution Plan (2026-05-28) |
There was a problem hiding this comment.
Add a single H1 before this section to keep heading levels sequential.
This starts at ## without a preceding #, which breaks the required heading structure for Markdown docs.
As per coding guidelines, "**/*.md: Use one H1 per file and keep heading levels sequential".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/projects/active/next-issues-execution-plan-2026-05-27.md at line 15,
Add a single top-level H1 above the existing "## Next Issues Execution Plan
(2026-05-28)" heading so the file contains one H1 and subsequent headings are
sequential; specifically insert a "# Next Issues Execution Plan (2026-05-28)"
(or a brief equivalent H1 title) immediately before the current "## Next Issues
Execution Plan (2026-05-28)" line to satisfy the "*.md: Use one H1 per file and
keep heading levels sequential" guideline.
| "issue_write", | ||
| "update_issue", | ||
| "get_issue", | ||
| "issue_read", |
There was a problem hiding this comment.
Update the agent-tools validator allowlist for issue_write/issue_read.
These new tool names are not in scripts/validation/validate-agents.js (validTools), so this config can be flagged as Unknown tool during validation.
Suggested fix
--- a/scripts/validation/validate-agents.js
+++ b/scripts/validation/validate-agents.js
@@
const validTools = [
@@
"todo",
"todowrite",
+ "issue_write",
+ "issue_read",
];🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@agents/mode-prd.agent.md` around lines 14 - 16, Add the new tool names
"issue_write" and "issue_read" to the validator allowlist by updating the
validTools array in scripts/validation/validate-agents.js so the agent config
entries ("issue_write", "update_issue", "issue_read") are recognized; locate the
validTools symbol in that file and append these two strings to the list
(preserving formatting and any existing sorting conventions) so validation no
longer flags them as Unknown tool.
🔍 Reviewer Summary for PR #494CI Status: ✅ Recommendations
|
1 participant
Summary
Closes #52 by replacing stale MCP issue tool references and completing the requested live backlog refresh + formal Wave 2 reprioritisation updates.
Changes
#52 MCP tool reference alignment
create_issue->issue_writeget_issue->issue_readagents/mode-prd.agent.md.github/prompts/create-github-issue-feature-from-specification.prompt.md.github/prompts/create-github-issues-feature-from-implementation-plan.prompt.md.github/prompts/create-github-issues-for-unmet-specification-requirements.prompt.md.github/prompts/my-issues.prompt.mdChangelog + next actions plan (requested first)
CHANGELOG.md(Unreleased) with:#64+ PR#461status#463#52MCP reference alignment.github/projects/active/next-issues-execution-plan-2026-05-27.mdwith:#61,#64)#52#464-#490Wave 2 reprioritisation pass (live issue updates)
#464-#490.#464,#465,#466,#467,#468,#469,#476,#480,#482) tostatus:ready.Validation
npm run lint:md -- CHANGELOG.md .github/projects/active/next-issues-execution-plan-2026-05-27.md .github/prompts/create-github-issues-feature-from-implementation-plan.prompt.md .github/prompts/create-github-issues-for-unmet-specification-requirements.prompt.md .github/prompts/create-github-issue-feature-from-specification.prompt.md .github/prompts/my-issues.prompt.md agents/mode-prd.agent.mdnpm run test:js(pre-commit hook)Summary by CodeRabbit
Documentation
Chores