agentleFS
Sign inStart free
OlliTapioOlliTapio/claude_skills/skills/test-on-main/SKILL.md

test-on-main

Skill0 starsChanged 18 days agoMITView on GitHub

Switch from a worktree to the main worktree with the in-progress branch, merge main, and run tests. Use when asked to "test on main worktree" or "switch to main worktree and test".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If merge conflicts occur, stop and inform the user.

    line 23
  2. Very specific:

    Run the project's quality checks (Makefile targets, package.json scripts, etc.).

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Test on Main Worktree

Exit worktree → checkout branch on main worktree → merge main → run tests.

Step 1: Exit worktree

Note the current branch name. If in a worktree, use ExitWorktree with action: "keep". If not in a worktree, skip.

Step 2: Checkout branch and merge main

git checkout <branch-name>
git fetch origin
DEFAULT_BRANCH=$(git remote show origin | grep 'HEAD branch' | cut -d' ' -f5)
git merge "origin/$DEFAULT_BRANCH" -m "Merge $DEFAULT_BRANCH into $(git branch --show-current)"

If merge conflicts occur, stop and inform the user.

Step 3: Run tests

Run the project's quality checks (Makefile targets, package.json scripts, etc.). Report results.

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.

Check your setup, free