3 ms·

I have a little ai-commit.sh as "send" in package.json which describes my changes and commits. Formatting has been solved by linters already. Neither my approac

by jwpapi 6mo ago

I have a little ai-commit.sh as "send" in package.json which describes my changes and commits. Formatting has been solved by linters already. Neither my approach nor OP approach are ground-breaking, but i think mine is faster, you also !p send (p alias pnpm) inside from claude no need for it to make a skill and create overhead.. Like thinking about it a pr skill is pretty much an antipattern even telling ai to just create a pr is faster. I think some vibe coders should let AI teach them some cli tooling

neilkakkar 6mo ago
OP here, I disagree, it's great to have a skill for cases where you have extra steps and want the agent to run some verification steps before making a PR. It's called making a PR, but it's not _just_ running the gh cli to make a PR. It's checking if I'm in a worktree, renames branches accordingly, adds a linear ticket if provided, generates a proper PR summary. I'm not optimising for how fast the PR is created, I want it to do the menial steps I used to do .
- jwpapi 6mo ago
  I have cli script for that as well. I have a cli script(wtq) that takes whatever is in my clipboard, creates a new worktree, cds into that worktree, installs dependencies, and then starts a claude session with the query in my clipboard. Once im done i can rune `wtf` and it it does the finish up work you described. It’s not about the workflow. A skill doesn’t make sense when you have a deterministic describable workflow, it’s just slower, because you have an interpretation and consuming step in there. You can just tell claude to turn the skill into a bash script and then alias it to whatever you like. A skill is useful if you have a variety of use cases that need to be interepretated and need a lot of the same utility.
  - neilkakkar 6mo ago
    I see what you mean - I have a setup-worktree script that does this, but I use the skill for knowing when to do bits and pieces. I would agree, if it were 100% deterministic script is much better.

by jwpapi 6mo ago

neilkakkar 6mo ago

OP here, I disagree, it's great to have a skill for cases where you have extra steps and want the agent to run some verification steps before making a PR. It's called making a PR, but it's not _just_ running the gh cli to make a PR. It's checking if I'm in a worktree, renames branches accordingly, adds a linear ticket if provided, generates a proper PR summary. I'm not optimising for how fast the PR is created, I want it to do the menial steps I used to do .

jwpapi 6mo ago
I have cli script for that as well. I have a cli script(wtq) that takes whatever is in my clipboard, creates a new worktree, cds into that worktree, installs dependencies, and then starts a claude session with the query in my clipboard. Once im done i can rune `wtf` and it it does the finish up work you described. It’s not about the workflow. A skill doesn’t make sense when you have a deterministic describable workflow, it’s just slower, because you have an interpretation and consuming step in there. You can just tell claude to turn the skill into a bash script and then alias it to whatever you like. A skill is useful if you have a variety of use cases that need to be interepretated and need a lot of the same utility.
- neilkakkar 6mo ago
  I see what you mean - I have a setup-worktree script that does this, but I use the skill for knowing when to do bits and pieces. I would agree, if it were 100% deterministic script is much better.