Add Ejentum Reasoning Harness MCP rules under Utilities#278
Conversation
Adds rules/ejentum-reasoning-harness-cursorrules-prompt-file/ with a .cursorrules and README.md that teach Cursor when to call each of the four ejentum-mcp cognitive harness tools (harness_reasoning, harness_code, harness_anti_deception, harness_memory), how to absorb the returned scaffold, and output discipline so bracketed fields shape internal reasoning instead of leaking into replies. Listed under Utilities, alongside the existing Helium MCP entry, since both are MCP-server-paired rule files.
|
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 as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds a new Cursor ChangesEjentum Reasoning Harness Integration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
rules/ejentum-reasoning-harness-cursorrules-prompt-file/.cursorrules (1)
96-96: 💤 Low valueAdd a trailing newline at the end of the file.
The file ends without a newline character after line 96. While not breaking, adding a trailing newline is a common convention for text files.
🤖 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 `@rules/ejentum-reasoning-harness-cursorrules-prompt-file/.cursorrules` at line 96, The file ends without a trailing newline; open the .cursorrules file (the file referenced) and add a single newline character at the end of the file so the file terminates with a trailing newline (ensure the last line 96 is followed by a newline and save the file).rules/ejentum-reasoning-harness-cursorrules-prompt-file/README.md (1)
51-51: 💤 Low valueAdd a trailing newline at the end of the file.
The file ends without a newline character after line 51. While not breaking, adding a trailing newline is a common convention for text files.
🤖 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 `@rules/ejentum-reasoning-harness-cursorrules-prompt-file/README.md` at line 51, The README.md file is missing a trailing newline at EOF; open the README.md (the file under rules/ejentum-reasoning-harness-cursorrules-prompt-file) and add a single newline character at the end of the file so the last line (line 51) ends with a newline, then save and commit the change.
🤖 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.
Nitpick comments:
In `@rules/ejentum-reasoning-harness-cursorrules-prompt-file/.cursorrules`:
- Line 96: The file ends without a trailing newline; open the .cursorrules file
(the file referenced) and add a single newline character at the end of the file
so the file terminates with a trailing newline (ensure the last line 96 is
followed by a newline and save the file).
In `@rules/ejentum-reasoning-harness-cursorrules-prompt-file/README.md`:
- Line 51: The README.md file is missing a trailing newline at EOF; open the
README.md (the file under
rules/ejentum-reasoning-harness-cursorrules-prompt-file) and add a single
newline character at the end of the file so the last line (line 51) ends with a
newline, then save and commit the change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e4ef8820-35d8-4e2a-90af-229039c79545
📒 Files selected for processing (3)
README.mdrules/ejentum-reasoning-harness-cursorrules-prompt-file/.cursorrulesrules/ejentum-reasoning-harness-cursorrules-prompt-file/README.md
|
Thanks for sending this. I am closing it because, as submitted, it reads more like promotion for an external tool/product/directory than neutral reusable Cursor rule content for this repo. If you still feel it should be added, please rework and resubmit it as a repo-focused contribution: actual rule content, neutral wording, minimal marketing copy, and a README entry that explains the Cursor workflow value. |
2 participants
Adds
rules/ejentum-reasoning-harness-cursorrules-prompt-file/with a.cursorrulesandREADME.mdthat teach Cursor when to call each of the fourejentum-mcpcognitive harness tools.What it does
harness_reasoningfor analytical / diagnostic / multi-step promptsharness_codefor codegen, refactor, review, debugging, architecture choicesharness_anti_deceptionwhen the prompt pressures the agent to validate, certify, or soften an honest assessmentharness_memoryonly when sharpening an observation already formed about cross-turn driftejentum-mcpMCP server in CursorWhere it goes
Listed under Utilities, alongside the existing
Helium MCPentry. Same shape: MCP server with a rules file teaching when to call each tool.About the project
ejentum-mcp)Thanks for maintaining this list.
Summary by CodeRabbit