[silverbucket]

Persists agent workflow preferences in .cursor/rules/github-pr-workflow.mdc:

• Check if a PR is merged before updating; if merged, branch from latest master and open a new PR
• New PRs always branch from latest master
• Continue on the same branch only while the PR is still open
• For silverbucket/* repos: do not use draft PRs unless work is incomplete

  

Summary by CodeRabbit

• Chores
  • Added GitHub pull request workflow guidance documentation for the repository.

[cursor]

Security review complete: no medium, high, or critical vulnerabilities found in this PR.

The change only adds a Cursor workflow rule for branch/PR handling; I did not identify an exploitable path involving attacker-controlled input, secret exposure, unsafe sinks, or authorization boundary changes.

  

_{Sent by Cursor Automation: Find vulnerabilities}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1ca71aab-28cd-4ba9-99e0-0dfbae211ac1

📥 Commits

Reviewing files that changed from the base of the PR and between 63d3221 and af20dc0.

📒 Files selected for processing (1)

• .cursor/rules/github-pr-workflow.mdc

---

📝 Walkthrough

Walkthrough

This PR adds Cursor rules documentation (.cursor/rules/github-pr-workflow.mdc) that defines GitHub PR workflow guidance for the repository and related silverbucket/* repos, covering branch creation strategy, merge-status handling, and draft PR policies.

Changes

GitHub PR Workflow Rules

Layer / File(s)	Summary
PR workflow rules documentation .cursor/rules/github-pr-workflow.mdc	Cursor rules document specifying: verify target PR branch merge status before branching, always branch from latest master for new PRs, permit continuation on unmerged branches, and restrict draft flag to genuinely incomplete work.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A doc for branches, clear and bright,
Check if merged before you write—
Master fresh, no drafts in jest,
Workflow rules to guide your quest!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding Cursor rules documentation for GitHub PR and git workflow guidance to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/github-pr-workflow-rules-91b9

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}