Skip to content

chore(repo): configure skrrt skills and GitHub Flow branching#8

Merged
truehazker merged 1 commit into
mainfrom
chore/setup-github-flow
Jun 20, 2026
Merged

chore(repo): configure skrrt skills and GitHub Flow branching#8
truehazker merged 1 commit into
mainfrom
chore/setup-github-flow

Conversation

@truehazker

Copy link
Copy Markdown
Owner

Summary

  • Add the skrrt:ship block to CLAUDE.md (commit/PR/release skill conventions + shared deployment/tagging rules).
  • Add a skrrt:branching block configured for GitHub Flow.
  • Codifies the migration off Gitflow: main is the only long-lived branch; all work flows through short-lived branches and squash-merged PRs targeting main.

Why

  • /commit and /pr previously found no branching strategy and prompted for /setup. This gives them a detectable GitHub Flow config so they target main automatically.
  • Reflects the completed migration: default branch is now main and develop has been deleted.

Test plan

  • grep skrrt:branching CLAUDE.md resolves and the heading reads "GitHub Flow".
  • A subsequent /commit and /pr detect GitHub Flow and target main without asking for /setup.

Notes

  • Docs-only change to CLAUDE.md; no code or template changes.

Co-Authored-By: Skrrt Bot bot@skrrt.sh

Add the skrrt ship block (commit/PR/release skill conventions and shared
deployment/tagging rules) and a GitHub Flow branching block to CLAUDE.md.
This codifies the migration off Gitflow: main is the only long-lived
branch, all work goes through short-lived branches and squash-merged PRs
targeting main, and develop/release/*/hotfix/* branches are no longer used.

Gives /commit and /pr a detectable branching strategy so they target main
instead of prompting for /setup.

Co-Authored-By: Skrrt Bot <bot@skrrt.sh>
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@truehazker, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 36 minutes and 8 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b632e8cb-b325-4cfe-b664-68a6e4a57939

📥 Commits

Reviewing files that changed from the base of the PR and between 8a5c5f3 and 0025454.

📒 Files selected for processing (1)
  • CLAUDE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/setup-github-flow

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

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

@truehazker
truehazker merged commit 6d58ff2 into main Jun 20, 2026
2 checks passed
@truehazker
truehazker deleted the chore/setup-github-flow branch June 20, 2026 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant