rad-source-control

Routes git commit, pull request, and worktree operations to reference guides.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-source-control-metalhexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rad-source-control
Source: https://github.com/MetalHexx/rad-orc-marketplace/tree/main/claude-plugin/skills/rad-source-control
Command: npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-source-control-metalhexx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating source-control operations across multi-repo projects is error-prone: commits land on wrong branches, duplicate PRs get opened on retries, and worktree cleanup is inconsistent. This Skill routes each source-control operation to a precise reference guide so agents perform commits, PRs, and worktree management correctly and idempotently. ## Core Features & Use Cases - Commit Guidance: Conventional-commit message formatting, deliberate staging, a pre-commit branch gate, and batched git calls to minimize context cost. - Pull Request Workflow: Idempotent PR detection with gh, draft PR creation from a final-review summary, and cross-linking of sibling PRs in multi-repo projects. - Worktree Management: Locate, create, and remove worktrees via the radorch CLI, with per-repo failure gating before source-control initialization. - Use Case: A coding agent finishing a task in its own worktree follows the commit reference to stage, verify the branch, commit, push if a remote exists, and report a structured result with the commit hash. ## Quick Start Ask the agent to commit the current task's work on its task branch and report the commit hash and push status.

Frequently Asked Questions about rad-source-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a conventional commit from a coding agent?▼

Derive a prefix from the task title (feat, fix, refactor, test, docs, or chore), format the header as {prefix}({taskId}): {title}, then stage, commit, and verify in one chained git call. Confirm HEAD is attached to the intended branch before committing.

How do I open a draft pull request with the gh CLI?▼

First check for an existing open PR with gh pr list --head to stay idempotent, then run gh pr create with --draft and --body-file pointing to a file containing the review summary. Capture the PR URL from the create output.

What happens if a commit lands on the wrong branch?▼

The pre-commit gate runs git symbolic-ref to confirm HEAD matches the intended branch. If it is detached or on a different branch, the agent stops and raises a Blocked report instead of committing, since wrong-branch commits are expensive to unwind.

Does the push step fail when a worktree has no remote?▼

No. The push step checks for an origin remote first; if none exists it prints a skip message and exits zero, which is treated as expected rather than a failure. Force-pushing and history rewriting are never allowed.

How are worktree creation failures handled in multi-repo projects?▼

worktree create isolates per-repo failures; if any repo entry has a non-null error, re-run create for just that repo before calling source-control init. Init is gated until every repo reports error: null.