docs(skills): ship-issue skill targets main, not test

[sweetmantech]

What

Updates the recoup-internal-dev-ship-issue skill so it tells the agent to open api PRs against main, not test.

Why

We're retiring the test → main staging step (it was always an auto-merge) to speed up the release cycle. PRs now go directly against main for api (and chat). Decision recorded in recoupable/chat#1829.

Changed (4 branch-target references)

• The loop diagram: PR target: test → PR target: main
• Recoup apiPRs targettest → `…target `main
• open the api PR (base test) → …(base main)
• The promote step: squash → test, then test → main via a release PR… → squash-merge directly to main

The TDD / test-suite references (pnpm test, red→green) are untouched — only the branch target changed.

Note (out of scope)

The recoup-internal-dev-issue-tracker skill has one test→main mention, but it's inside a historical example closure note (a real past PR that did go through test) — left as-is to avoid falsifying the example. Say the word if you'd rather genericize it.

🤖 Generated with Claude Code

---

Summary by cubic

Update recoup-internal-dev-ship-issue so api PRs target main, removing the test → main stage to speed up releases. Tightens the doc/checklist to squash-merge to main and require updating the tracking issue’s PR-matrix row at PR-open time (repo#TBD → live ref + status).

• Refactors
  • Removed restated “Principles”, vestigial promote/release-scope notes, the redundant Vercel CLI line, and duplicate mentions of the branch-target rule.
  • Corrected generated-JSON guidance: favor anchored text edits when round-tripping fails; keep diffs additive and re-validate.
  • Added a preview-auth note: preview envs may use different auth/secrets; use preview-scoped creds to avoid 401s.

^{Written for commit c43355f. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

@sweetmantech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5043b447-d21b-4a3c-a8fa-355e4a1fd833

📥 Commits

Reviewing files that changed from the base of the PR and between 435a335 and c43355f.

📒 Files selected for processing (1)

• skills/recoup-internal-dev-ship-issue/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/dev-skills-pr-against-main

---

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

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

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}