docs: add worktrunk Agent Skills file#776
Conversation
jaydenfyi
force-pushed
the
feature/add-worktrunk-skill
branch
from
1c4b5a4 to
06b91b1
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1c4b5a4c5c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| wt switch --create feature # Create worktree and branch | ||
| wt switch feature # Switch to worktree | ||
| wt list # Show all worktrees | ||
| wt merge # Squash, rebase, merge to main, remove worktree |
There was a problem hiding this comment.
The quick-start comment says wt merge “merge to main,” but the tool targets the default branch, which may be master or another name. In repos where the default branch isn’t main, this instruction is misleading for users/agents and conflicts with the terminology guidance in AGENTS.md (“default branch” vs “main branch”). Consider changing this to “merge to default branch” to match actual behavior and the project terminology rules.
Useful? React with 👍 / 👎.
|
is we currently have a skill in the Claude Code plugin; keen to allow other agents to use it too... |
Ah apologies, I was unaware the Claude plugin already had a skill file defined 🤦♂️ Definitely very early, I've only just seen some mentions of it in my Twitter bubble over the last few days. Here's a blog post from 12 hours ago 😅 https://vercel.com/changelog/introducing-skills-the-open-agent-skills-ecosystem But I would bet on it gaining adoption based on it being interoperable with any coding agent, and by virtue of triangle companies influence. I don't personally use Claude Code which is why it's only recently caught my attention as Codex and other agents are starting to add support for skills. Happy for you to close this if it's not desirable yet or not documented how you'd like. I think I aimed for it to be pretty specific to using the worktrunk CLI commands directly, which I guess is quite a bit different to the existing one in the Claude plugin. |
|
ok, let's keep an eye on how things evolve on the non-claude-code approach to installing skills? |
|
I took a look at the I can't seem to work out how to tell it where our skills are! we don't want our we could merge #480, which might help it find the actual worktrunk skill, but we still have the if we can make unobtrusive changes to the repo and become compatible, that would be great! |
|
An update: the skills CLI now respects an |
2 participants
Add an Agent Skills file to better allow AI agents to create and manage their own worktrees.
Would allow people to call
for people to easily add the skill to their own skills directories.
Just for consideration. I can see how this comes with extra/duplicate documentation overhead as well.