Add manifest-dev plugin#619
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdded a new row to the “All Plugins” table in README.md documenting the ChangesREADME plugin listing update
Estimated code review effort: 1 (Trivial) | ~2 minutes Related PRs: None mentioned. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@README.md`:
- Line 209: The README table row for manifest-dev has a cell count mismatch with
the surrounding two-column table. Update the table structure so the row in the
markdown fits the same column count as the header, using the manifest-dev entry
as the reference point; either add a third header column to match the extra
field or merge that extra text into one of the existing cells so renderers
display the plugin entry correctly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
Drop the stray unlabeled cell so the row matches the two-column Plugin | Description table (resolves MD056).
2 participants
What problem it solves: coding agents start building before the problem is understood and report done on self-assessment. manifest-dev separates understanding (/figure-out), acceptance definition (/define), and verified execution (/do) — one independent verifier per criterion decides done.
Who uses it: developers handing larger tasks to a coding agent who want a stop condition they can trust.
Attribution: original work, doodledood/manifest-dev (MIT).
Example: /figure-out "why do half my background jobs silently stall?" — it investigates the repo and presses the load-bearing question before any fix. Individual skills install via npx skills add doodledood/manifest-dev --skill figure-out.
Summary by CodeRabbit
manifest-deventry to the “All Plugins” list in the README./figure-out adversarial understanding,/define acceptance criteria, and/do execution(with an independent verifier per criterion).