docs(agents): capture the fork's upstream sync workflow as a skill - #10
Conversation
The sync workflow existed only as git history patterns, so every sync re-derived the same guardrails from scratch. Encoding them as a skill makes each sync repeatable and protects the fork's divergences, migration id blocks, and merge-based history from being regressed by an uninformed merge. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryLow Risk Overview The skill encodes the repeatable sync workflow: merge-not-rebase, branch naming, reading Reviewed by Cursor Bugbot for commit d1aaa7a. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughAdds a skill document describing how to merge upstream ChangesUpstream synchronization workflow
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
✨ 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 |
trogonstack-prefix so fork-only skills read as fork-only on sight and can never collide with a skill name upstream adds, mirroring theMigrations/forkanddocs/forkconventions.