agentleFS
Vlor999Vlor999/pr-radar/.claude/skills/worktree/SKILL.md

worktree

Skill0 starsChanged 13 days agoMITView on GitHub

Implement one feature or fix of PR Radar in an isolated git worktree, from branch to GitHub PR on dev (checks, logical commits, push, PR, then demo). Use when asked to implement something in a worktree or to start a worktree for a task.

  • Commits and pushes

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use worktree-merge, resolve-conflicts and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • leessjuSkill

    worktree-merge

    Squash-merge the current worktree branch into the main branch (or a specified target). Analyzes git history and source code to craft a comprehensive commit message.

    Also in 3 projects that use this

  • ralphkraussSkill

    resolve-conflicts

    Resolve git merge conflicts or re-apply changes from a stale branch onto current main. Use when user says "resolve conflicts", "merge conflicts", "rebase branch", "branch is behind", "re-apply changes", "port branch", or a branch is too far behind main to merge cleanly.

    Also in 5 projects that use this

  • SentrySkill

    e2e

    Run E2E tests for Sentry JavaScript SDK test applications

    Also in 5 projects that use this

  • hdcolaSkill

    pr-comments

    Fetch unresolved review comments from a GitHub PR or mark comments as resolved. Use this when managing PR review feedback, checking pending comments, or marking review threads as resolved. Supports GitHub URLs or explicit owner/repo/PR-number from anywhere, or PR number auto-detection from within a git repository.

    Also in 3 projects that use this

  • Google CloudSkill

    contributing

    Guides the developer workflow for contributing to Race Condition. Use when setting up pre-commit hooks, running tests before a PR, understanding code style requirements, or preparing a contribution.

    Also in 3 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the task is missing or unclear, ask before continuing.

    line 12
  2. Distinctive:

    Do the simplest thing that works, reuse what the repo has.

    line 35
  3. Very specific:

    Follow CLAUDE.md (stack, security rules, site/ with mock data only).

    line 36
  4. Distinctive:

    Run the checks of CLAUDE.md until green:

    line 41
  5. Very specific:

    Never push red, never use --no-verify.

    line 48
  6. Very specific:

    Use logical-commit-sequencer to split the work into atomic commits, ordered by dependency.

    line 54
  7. Very specific:

    No question in the body. An open decision goes to the user in the conversation and is settled before the PR is opened.

    line 78

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Implement one task in an isolated worktree, up to the PR on dev. One task = one worktree = one PR.

Signature: /worktree <GitHub issue number or task description>

If the task is missing or unclear, ask before continuing.

1. Read the task

With an issue number: gh issue view <n>. If the work already exists on dev, say so and do only what is really left.

2. Create the worktree

Branch: <type>/<feature-slug> (e.g. fix/quota-refresh), type = Conventional Commit type. Base: origin/dev. Stacked PR (only when the user asks): base on the parent feature branch instead (origin/<parent branch>).

git fetch origin
git worktree add .claude/worktrees/<feature-slug> -b <branch> origin/dev
cd .claude/worktrees/<feature-slug> && npm ci

Work only inside this worktree.

3. Implement

  • Do the simplest thing that works, reuse what the repo has.
  • Follow CLAUDE.md (stack, security rules, site/ with mock data only).
  • Stay inside the task scope. No refactor that was not asked for.

4. Verify

Run the checks of CLAUDE.md until green:

npm run typecheck && npm test
(cd src-tauri && cargo clippy -- -D warnings && cargo test)

Never push red, never use --no-verify. Green checks are the only gate before commit, push and PR: do not wait for the user. The demo and the user's validation come after the PR, before merge (step 7).

5. Commit and push

Use logical-commit-sequencer to split the work into atomic commits, ordered by dependency. Conventional Commits, with the Co-Authored-By trailer. Then:

git push -u origin <branch>

6. Open the PR

gh pr create --base dev --title "<conventional commit>" --body "..."
# stacked PR: --base <parent branch>

Body:

## Intent
<What the PR does and why, 1-2 sentences. `Closes #<n>` if from an issue.>

## Choices and caveats
- <Each decision taken, as a statement.>

No question in the body. An open decision goes to the user in the conversation and is settled before the PR is opened. Never add or request a reviewer (--reviewer).

7. Demo, review, merge

  • Visible change: demo skill (npm run demo) and explicit validation by the user before merge. As a subagent, hand back: the orchestrator runs the demo.
  • Review fixes (mr-review § Orchestrated loop): new commits on the same branch, checks green, git push. Never --amend, never force-push.

8. Report

Give the PR URL, the decisions taken, and the work left after the PR. Remove the worktree once the PR is merged: git worktree remove .claude/worktrees/<feature-slug>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.