Add Xquik MCP workflow rule and repair MCP frontmatter - #317
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds a Cursor rule for configuring and using Xquik’s remote MCP server for public X research and explicitly requested account workflows, registers it in the README, and quotes a glob pattern in another Cursor rule. ChangesXquik MCP X Research Rule and Registration
Cursor Rule Metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
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 `@rules/xquik-mcp-x-research.mdc`:
- Line 3: The glob pattern `globs: **/*` on line 3 is invalid YAML because the
`**` sequence is interpreted as an alias indicator, and the pattern is too broad
as it matches every file in every directory. Fix this by either properly quoting
the pattern as `'**/*'` if a universal pattern is truly needed, or better yet,
narrow it to specific file extensions relevant to the X/Twitter research rule
following the repository's documented format (e.g., patterns like **/*.ts,
**/*.tsx for TypeScript files). Refer to the repository's README for the correct
documented format for glob patterns in this rule file.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4ab986fc-f791-4b8b-8a39-0bff64e6a33c
📒 Files selected for processing (2)
README.mdrules/xquik-mcp-x-research.mdc
|
Rebuilt the focused 3-file change on the current The independent fix remains linked to #344. It quotes the Helium MCP rule glob so its YAML frontmatter parses without changing its intended scope. Validation rerun on the exact submitted tree:
All repository checks pass. The earlier CodeRabbit thread remains resolved. |
0d83a00 to
106e5a4
Compare
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 `@rules/xquik-mcp-x-research.mdc`:
- Line 36: Update the mutation-confirmation instruction in the rules content to
require confirming the authenticated connected-account identity alongside the
target and payload before any X write, including publishing, deleting,
following, messaging, or account-state changes.
- Line 35: Clarify the Xquik pagination guidance in the rule containing
“has_more” and “next_cursor”: pagination is response-driven and
endpoint-specific, so pass “next_cursor” using “cursor” for X data
search/timelines, “after” for extractions/events/radar/draws, or “afterCursor”
for drafts while preserving existing filters and limits. Update the guidance
around the scoped request options to pass “method”, “query”, and “body” whenever
the discovered endpoint requires them or the task needs date windows, filters,
limits, or mutation payloads.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 342c5171-1c1f-4807-aab1-8c23190e7b34
📒 Files selected for processing (3)
README.mdrules/helium-mcp-cursorrules-prompt-file.mdcrules/xquik-mcp-x-research.mdc
🚧 Files skipped from review as they are similar to previous changes (1)
- README.md
106e5a4 to
7525f40
Compare
Summary
Adds a Cursor Project Rule for using Xquik through MCP. The rule covers current X research, exports, monitoring, and explicit connected-account workflows. It uses Cursor's native OAuth 2.1 flow and keeps mutations user-directed.
Also fixes invalid YAML frontmatter in the existing Helium MCP rule.
Contribution Type
rules/*.mdcruleValue To Cursor Users
Cursor users get a reusable, OAuth-first rule for discovering and executing Xquik operations without inventing live X data. The rule explains narrow reads, pagination, mutation boundaries, secret handling, errors, and evidence-based responses.
The Helium fix preserves its intended universal scope while making its frontmatter valid YAML.
Added Or Changed Files
rules/xquik-mcp-x-research.mdc: Adds the complete Xquik MCP workflow rule.rules/helium-mcp-cursorrules-prompt-file.mdc: Quotes its wildcard glob so YAML parsers can read the frontmatter.README.md: Registers the Xquik rule under Database and API.Quality Checklist
react-typescript.mdc.rules/*.mdcfiles include frontmatter with a non-emptydescription, relevantglobs, andalwaysApply: falseunless the rule is universal.Notes For Maintainers
The connection flow and tool behavior were verified against the current public Xquik MCP documentation and discovery contracts. The rule directs Cursor to the live tool list when the contract changes.
The independent Helium defect is reproduced in #344.
Fixes #344.
Validation:
npm test(84 tests)npm run check:awesome-listnpm run check:repo-hygienenpm run check:readme-hygienenpm run check:rule-hygienenpm run check:issue-template-policynpm run check:repo-securitygit diff --checkSummary by CodeRabbit