fix invalid yaml in rules globs

[martinklepsch]

Just saw your blog post and noticed the frontmatter isn't quite correct.

I've also asked on the cursor forum to verify this but essentially the format for the globs is invalid YAML currently

Summary by CodeRabbit

• Refactor
  • Updated the configuration file to use an array structure for file pattern definitions, improving clarity and consistency while maintaining the same functionality.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 09b5a32

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The change updates the configuration in .cursor/rules/writing-tasks.mdc by modifying the globs property. Instead of using a comma-separated string to specify file patterns, the property now uses an array of strings. The file patterns remain unchanged, and no public or exported entities have been modified.

Changes

File(s)	Change Summary
.cursor/rules/writing-tasks.mdc	Changed globs property from a comma-separated string to an array of strings, keeping the same file patterns.

Possibly related PRs

• cursor rules: Adds js to file paths and fixes typos #1803: Alters the globs field by including additional file types, showing a strong code-level connection with this change.

Suggested reviewers

• ericallam

Poem

I'm a rabbit with a hop so bright,
Arrays now make the globs just right.
No more commas in a tangled mess,
Only clear strings to bless our text.
I nibble on code with pure delight,
Celebrating config updates all night!

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 174484f and 09b5a32.

📒 Files selected for processing (1)

• .cursor/rules/writing-tasks.mdc (1 hunks)

[coderabbitai]

🛠️ Refactor suggestion

Convert globs to a Valid YAML Array

The updated globs property now uses a YAML array of strings instead of a comma-separated string, which resolves the invalid YAML issue and improves readability. Ensure that any tools or scripts parsing this configuration are updated to work with the array format.

[martinklepsch]

Please ignore this I was confused