[absolutepraya]

Summary

• require agents to use the absolute path printed by wt new as the working directory for all follow-up work
• keep task changes out of the main worktree unless the user explicitly asks otherwise
• extend the WT skill evals with a post-creation follow-up scenario

Verification

• WT skill quick validation passed
• evals JSON validation passed
• git diff --check passed

The existing WT skill already documents installation, command usage, aliases, shell integration, project configuration, safety rules, and validation guidance.

Summary by CodeRabbit

• Documentation

  • Clarified that work following worktree creation should continue in the newly created worktree unless explicitly overridden.
  • Added guidance to use the absolute path provided during worktree creation rather than inferring paths from worktree names.

• Tests

  • Expanded evaluation coverage for creating, inspecting, testing, and continuing work exclusively within the new worktree.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 220a5405-323f-4844-9680-60636875032e

📥 Commits

Reviewing files that changed from the base of the PR and between 50d826d and dd65dd3.

📒 Files selected for processing (2)

• skills/wt/SKILL.md
• skills/wt/evals/evals.json

---

📝 Walkthrough

Walkthrough

The worktree skill now requires follow-up work to use WT’s printed absolute path. The evaluation data adds expectations and a case for inspection, testing, and continued work in the created worktree.

Changes

Worktree handoff

Layer / File(s)	Summary
Worktree handoff guidance skills/wt/SKILL.md	Follow-up work must use the newly created worktree unless explicitly overridden. WT’s printed absolute path is authoritative for commands and child processes.
Worktree handoff evaluation skills/wt/evals/evals.json	The evaluations require absolute-path use and add a case covering worktree creation, inspection, testing, and continued work outside the main worktree.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch absolutepraya/skill-guidance

---

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