feat(cursor): maintain-herdr fork ops project skill

[OnlineChef]

Fork maintenance playbook as a project skill (repo .cursor/skills convention, indexes regenerated):

• PR autopilot loop + checks gate
• Full-clone rebase playbook (shallow-clone gotcha, stale rebase-state abort)
• Conflict patterns: generated cursor indexes take main, code conflicts by hand
• Draft triage (cursor drafts vs WIP like freebuff/*)
• Quality-gate redirect to herdr-quality-ci-remediation
• sofie memory constraints + commit conventions

refs #87

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}

Greptile Summary

This PR adds a Cursor skill for maintaining the Herdr fork and registers it in the Markdown and YAML skill indexes. The fresh-clone rebase instructions have a reproduced failure: a normal clone creates only origin, but the playbook immediately resets to fork/main before configuring or fetching fork, so maintainers cannot start the documented rebase flow.

Confidence Score: 3/5

Not safe to merge until T-Rex findings are addressed.

An isolated Git reproduction confirmed that the documented command sequence fails with only the remote created by a conventional clone, while adding and fetching fork makes the same reset succeed.

T-Rex reproduced 2 failing behaviors at runtime in .cursor/skills/maintain-herdr/SKILL.md; the change needs fixes before it is safe to merge.

Files Needing Attention: .cursor/skills/maintain-herdr/SKILL.md

T-Rex Logs

What T-Rex did

• T-Rex executed the local Git reproduction script to reproduce the posted P1 finding.
• T-Rex produced a proof for the posted P1 finding, aligning with the review comment.
• The before/after contract validation shows that adding and fetching the fork creates fork/main and allows the reset to succeed.
• The configured logs demonstrate the transition from a fresh clone reset failure to a successful reset after forking, supporting the validation.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Fresh-clone rebase instructions reference an unconfigured fork remote

   • Bug
     • The playbook instructs maintainers to clone and immediately reset to fork/main, but a conventional clone creates only origin, so the procedure stops before it can rebase.
   • Cause
     • The instructions omit setup and fetching of the fork remote before its first use.
   • Fix
     • Add documented fork remote configuration and a fetch that creates fork/main before line 39, or consistently use the intended configured remote.

   _{Ran code and verified through T-Rex}

Prompt To Fix All With AI

### Issue 1
.cursor/skills/maintain-herdr/SKILL.md:33-40
**Fresh clone lacks required remote**

The prescribed `git clone https://github.com/OnlineChefGroep/herdr.git` creates only the `origin` remote. The next command relies on `fork/main`, but no `fork` remote or tracking ref has been configured, so `git reset --hard fork/main` stops the rebase procedure with an unknown-revision error. Document setup and fetching of `fork` before its first use, or use the remote established by the clone consistently.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "feat(cursor): add maintain-herdr fork op..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 47 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a4730300-02ee-4801-bec8-3d57320a8676

📥 Commits

Reviewing files that changed from the base of the PR and between c940c33 and aeb2325.

📒 Files selected for processing (3)

• .cursor/INDEX.md
• .cursor/skills/.index.yaml
• .cursor/skills/maintain-herdr/SKILL.md

---

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

[greptile-apps]

Fresh clone lacks required remote

The prescribed git clone https://github.com/OnlineChefGroep/herdr.git creates only the origin remote. The next command relies on fork/main, but no fork remote or tracking ref has been configured, so git reset --hard fork/main stops the rebase procedure with an unknown-revision error. Document setup and fetching of fork before its first use, or use the remote established by the clone consistently.

Artifacts

Executable local Git reproduction script

• This script creates local bare Git repositories and runs the documented reset before and after configuring `fork`, proving the behavior without network access—the defect is reproducible.

Fresh clone reset failure log

• This captured execution lists only `origin` and shows `git reset --hard fork/main` failing with exit code 128 and an unknown-revision error—the documented fresh-clone procedure fails.

Configured fork reset success log

• This captured execution adds and fetches `fork`, then shows the same reset completing successfully—the missing fork setup is the required correction.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: .cursor/skills/maintain-herdr/SKILL.md
Line: 33-40

Comment:
**Fresh clone lacks required remote**

The prescribed `git clone https://github.com/OnlineChefGroep/herdr.git` creates only the `origin` remote. The next command relies on `fork/main`, but no `fork` remote or tracking ref has been configured, so `git reset --hard fork/main` stops the rebase procedure with an unknown-revision error. Document setup and fetching of `fork` before its first use, or use the remote established by the clone consistently.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.