I think the point is that I don't have to remember the command. I just have to tell my agent in plain-English to do X.

For example, we're dragging our feet on Github Config as Terraform at our org so in the meantime I've been using Claude + the gh cli to deploy changes across repos. I don't need to know / remember the gh cli command to pull or push a ruleset, or script a loop in Bash, I just have to say

> Claude pull the ruleset from <known good repo> and push it to <repo 1>, <repo 2>, <repo 3>

The CLI is also nice because it abstracts away authentication. I have another flow which doesn't have a CLI and Claude is more than happy to interpolate the API key that it read from a config file into the chat history (horrifying).

▲

porphyra 2 days ago | parent [-]

Exactly. Talking in plain English is a lot less mental overhead than reading the man page and figuring out the right command. Nowadays I just use AI instead of remembering ffmpeg commands too. Your point about authentication is important too.

▲

deadbabe 2 days ago | parent [-]

What the hell am I reading, you guys know you can make little scripts for commands with prefilled options or even take in parameters?

	▲	jillesvangurp a day ago \| parent [-]
		That's what the coding agent does if you ask it to record a skill. Yes I can do that manually. But I'll get it wrong a few times before I get it right and waste half an hour in the documentation, if I'm lucky. Or I just go, "I just created this cloudflare domain. Deploy the site via gh actions to cloudlare pages whenever I push to main. here are my credentials; put them in Github secrets." Or something similarly high level. The clever thing here is not doing things manually but make sure you generate automation and scripts if you are going to do the same things more often along with skill files detailing how and when to call shit.