“Build my branch and deploy it to QA” sounds like one request. On a shared Jenkins instance it means finding the right jobs, specifying the code branch and the deploy-config branch in different places, getting a version out of the build, and passing that version to the deploy job. If something fails, someone has to work out which lines in the console matter.
The same Jenkins instance also held production deploy jobs. A short request in the terminal assistant people already used made sense as the interface. The skill covers build, preview, and deploy to non-production, with a way to run tests and roll back when needed. Each step surfaces the Jenkins details that matter before the next one starts.
The assistant drives a small CLI
The plugin lives in an internal marketplace monorepo. The stable interface is the skill, which describes when to load it, what to ask the user, and what to do next. Behind it is a Bash CLI that makes the Jenkins requests using curl and jq.…