update-playbooks
starsforks
How to install update-playbooks?
vinta/hal-9000/update-playbooks
$npx -y skills add vinta/hal-9000 --skill update-playbooks(project) Use when bumping hardcoded tool versions in playbooks/roles/ to their latest releases
SKILL.md
| 1 | # Update Playbooks |
| 2 | |
| 3 | Bump every version pinned in `playbooks/roles/*/tasks/main.yml` to the newest release of its current **release line**, then commit per role. |
| 4 | |
| 5 | A **release line** is the version prefix a project treats as a stable series: Node `24.x`, Python `3.14.x`, kubectl `1.35.x`, nvm `0.40.x`. Every bump stays inside the line (`24.15.0` -> `24.18.0` is in-line for Node because Node's line is the major). When a newer line exists (Node 26, Python 3.15, kubectl 1.36), keep the pin on its current line and report the newer line in the final summary so the user can decide. |
| 6 | |
| 7 | ## 1. Scan |
| 8 | |
| 9 | ```bash |
| 10 | grep -rn -E '[0-9]+\.[0-9]+\.[0-9]+' playbooks/roles/*/tasks/main.yml |
| 11 | ``` |
| 12 | |
| 13 | Versions hide in task names, command bodies, and download URLs. Done when every pinned version is listed with its role, current release line, and the doc URL from the `#` comment above its task. |
| 14 | |
| 15 | ## 2. Look up the latest release |
| 16 | |
| 17 | For each pin, get the release listing from that comment URL: |
| 18 | |
| 19 | - `github.com/OWNER/REPO` link: `gh api repos/OWNER/REPO/releases --jq '.[].tag_name'`, then take the newest tag inside the line |
| 20 | - any other link: WebFetch the URL and read the newest in-line version off the page |
| 21 | |
| 22 | Done when every pin has a latest in-line version confirmed from its listing today. A version recalled from training data is stale by definition. |
| 23 | |
| 24 | ## 3. Edit |
| 25 | |
| 26 | For each pin whose line has a newer release, replace the old version at every occurrence in the role: the task `name:`, each command line, and any URL. Done when grepping the file for the old version returns nothing. |
| 27 | |
| 28 | ## 4. Verify and commit |
| 29 | |
| 30 | Run `make lint`. Then create one commit per changed role with the `commit` skill, passing what moved, e.g. `bump kubectl to v1.35.7`. Close with a summary: each pin's old -> new version, pins already current, and any newer release lines waiting on the user. |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
