Open
Conversation
Adds a cursor rule for OSOP (Open Standard for Orchestration Protocol) session logging, which records AI coding sessions as structured .osop + .osoplog.yaml workflow files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
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 (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughAdded documentation and cursor-rule prompts to record AI coding sessions as OSOP workflow ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
- Update .cursorrules to reference windsurf instead of cursor - Add rules-new/osop-session-logging.mdc in the newer rule format Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
rules-new/osop-session-logging.mdc (1)
1-5: Consider whether global application is necessary.This rule uniquely sets
alwaysApply: truewith an emptyglobs:field, applying it globally across all files. While most.mdcfiles target specific file types with glob patterns, a few rules (Gitflow Workflow, Code Quality Guidelines) also use empty globs for cross-cutting concerns.Since OSOP session logging is triggered by task completion rather than file type, the global scope is a deliberate design choice. However, verify whether this should instead target specific file types where sessions are most valuable (e.g., source code directories) to reduce potential noise in non-code contexts.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@rules-new/osop-session-logging.mdc` around lines 1 - 5, The rule "OSOP session logging" currently sets alwaysApply: true with an empty globs:, applying globally; decide whether to keep global scope or restrict it by adding appropriate glob patterns and/or removing alwaysApply. If you want cross-cutting behavior, add a brief justification in the rule description that session logging is triggered by task completion (not file type) and keep alwaysApply: true; otherwise, remove alwaysApply and populate globs with targeted patterns (e.g., source directories or file extensions where session logs are valuable) so the rule only runs for relevant code artifacts, and update the rule description to note the change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@rules-new/osop-session-logging.mdc`:
- Line 58: The runtime metadata currently sets agent: "windsurf" which is
incorrect for Cursor AI; update the runtime agent value (replace the string
"windsurf" with "cursor" in the runtime section where agent: "windsurf" is
defined) so session logs correctly reflect the Cursor agent.
- Line 22: The tags metadata in this rule uses the wrong agent name
("windsurf"); update the tags array on the line containing tags: [windsurf,
<relevant-tags>] to use "cursor" instead of "windsurf" so the tag reads tags:
[cursor, <relevant-tags>]—this ensures the agent name in the rule metadata (the
tags line) is consistent with Cursor AI naming.
In `@rules/osop-session-logging-cursorrules-prompt-file/.cursorrules`:
- Around line 55-58: The runtime metadata currently sets agent: "windsurf" which
mismatches Cursor AI; update the agent field in the .cursorrules runtime block
to "cursor" so session logs correctly reflect the AI editor in use (locate the
agent: "windsurf" entry in the runtime/node_records section and replace it with
agent: "cursor").
- Line 19: The tags line in the .cursorrules file currently includes the agent
name "windsurf" which is inconsistent for a Cursor-specific rule; edit the tags
entry (the line starting with "tags:") to replace "windsurf" with "cursor" (or
add "cursor" and remove "windsurf") so the rule's tags accurately reflect the
Cursor agent.
---
Nitpick comments:
In `@rules-new/osop-session-logging.mdc`:
- Around line 1-5: The rule "OSOP session logging" currently sets alwaysApply:
true with an empty globs:, applying globally; decide whether to keep global
scope or restrict it by adding appropriate glob patterns and/or removing
alwaysApply. If you want cross-cutting behavior, add a brief justification in
the rule description that session logging is triggered by task completion (not
file type) and keep alwaysApply: true; otherwise, remove alwaysApply and
populate globs with targeted patterns (e.g., source directories or file
extensions where session logs are valuable) so the rule only runs for relevant
code artifacts, and update the rule description to note the change.
🪄 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: 55afbff6-ec7a-4ed3-8274-d3cc8100da96
📒 Files selected for processing (3)
README.mdrules-new/osop-session-logging.mdcrules/osop-session-logging-cursorrules-prompt-file/.cursorrules
rules/osop-session-logging-cursorrules-prompt-file/.cursorrules
Outdated
Show resolved
Hide resolved
rules/osop-session-logging-cursorrules-prompt-file/.cursorrules
Outdated
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.osop+.osoplog.yamlworkflow filesWhat's included
rules/osop-session-logging-cursorrules-prompt-file/.cursorrules— the cursor rule fileLinks
Summary by CodeRabbit