How do I install the Update Collection skill?

Run npx skillmds@latest add 3a2dev/update-collection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Collection safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Collection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Collection free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Collection?

3A2DEV (@3a2dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Collection by 3a2dev — Agent Skill

Name: Update Collection
Author: 3A2DEV

Update Collection

Update an existing Ansible collection. Triggered by /update-collection. Supports updating galaxy.yml metadata, adding roles or plugins, bumping version, and updating CHANGELOG. Shows a unified diff per file before writing and waits for explicit user confirmation.

3A2DEV 73bf287 3.4 KB Updated Sep 17, 2026

File contents

update-collection

Update an existing Ansible collection. Always shows a diff and waits for confirmation before writing.

Required Inputs

collection identification — namespace.name or path (resolved from discovery)
change_description — What to change (e.g., "bump version to 1.1.0", "add a new filter plugin", "update the description in galaxy.yml")

Behavior

Step 1 — Discovery

Locate the collection via discovery (references/discovery.md).

Step 2 — Load Target Files

Read only the files relevant to the requested change.

Step 3 — Apply Change

Apply the requested change:

Preserve all existing fields and structure
Use templates from references/collection.md for new files
All new module/plugin code follows the complete skeleton format from references/plugins.md
Keep test and usage guidance aligned with references/testing.md

Step 4 — Show Unified Diff (per file)

For each modified or created file, show the diff:

--- collections/ansible_collections/myorg/infra/galaxy.yml (original)
+++ collections/ansible_collections/myorg/infra/galaxy.yml (proposed)
@@ -3,7 +3,7 @@
 namespace: myorg
 name: infra
-version: 1.0.0
+version: 1.1.0
 readme: README.md

Then ask: "Apply these changes? (yes/no)"

Step 5 — Write on Confirmation

If yes: write all modified/created files.
If no: ask what to change and loop back.

Step 6 — Final Output

Show updated file tree:

find <collection_path> -type f | sort

Suggest next step:

Next step: Run `ansible-galaxy collection build` to test the collection build
           and `ansible-galaxy collection install <tarball> --force` to test locally.

Change Types Supported

Change requested	Files to modify	How to handle
Bump version	galaxy.yml, CHANGELOG.md	Update version field; add CHANGELOG entry with date
Update description	galaxy.yml	Update description field
Add dependency	galaxy.yml	Append to dependencies dict with version range
Add role	roles/	Create role dir using new-role logic; update galaxy.yml tags if needed
Add module	plugins/modules/.py	Create complete module skeleton from `references/collection.md`
Add filter plugin	plugins/filter/.py	Create FilterModule skeleton
Add lookup plugin	plugins/lookup/.py	Create LookupBase skeleton
Update README	README.md	Apply requested textual change
Update meta/runtime.yml	meta/runtime.yml	Update requires_ansible or plugin_routing
Add CHANGELOG entry	CHANGELOG.md	Prepend new version entry

Version Bump Rules

PATCH bump (1.0.x → 1.0.x+1): bug fixes, no behavior changes
MINOR bump (1.x → 1.x+1.0): new features, backward-compatible
MAJOR bump (x → x+1.0.0): breaking changes — warn the user that this affects consumers

When bumping version, always add a CHANGELOG entry:

## [1.1.0] - 2026-03-31

### Added
- <description of what was added>

### Changed
- <description of what was changed>

---name: update-collectiondescription: Update an existing Ansible collection. Triggered by /update-collection. Supports updating galaxy.yml metadata, adding roles or plugins, bumping version, and updating CHANGELOG. Shows a unified diff per file before writing and waits for explicit user confirmation.---# update-collectionUpdate an existing Ansible collection. Always shows a diff and waits for confirmation before writing.---## Required Inputs1. **collection identification** — `namespace.name` or path (resolved from discovery)2. **change_description** — What to change (e.g., "bump version to 1.1.0", "add a new filter plugin", "update the description in galaxy.yml")---## Behavior### Step 1 — DiscoveryLocate the collection via discovery (`references/discovery.md`).### Step 2 — Load Target FilesRead only the files relevant to the requested change.### Step 3 — Apply ChangeApply the requested change:- Preserve all existing fields and structure- Use templates from `references/collection.md` for new files- All new module/plugin code follows the complete skeleton format from `references/plugins.md`- Keep test and usage guidance aligned with `references/testing.md`### Step 4 — Show Unified Diff (per file)For each modified or created file, show the diff:```--- collections/ansible_collections/myorg/infra/galaxy.yml (original)+++ collections/ansible_collections/myorg/infra/galaxy.yml (proposed)@@ -3,7 +3,7 @@ namespace: myorg name: infra-version: 1.0.0+version: 1.1.0 readme: README.md```Then ask: **"Apply these changes? (yes/no)"**### Step 5 — Write on Confirmation- If **yes**: write all modified/created files.- If **no**: ask what to change and loop back.### Step 6 — Final OutputShow updated file tree:```bashfind <collection_path> -type f | sort```Suggest next step:```Next step: Run `ansible-galaxy collection build` to test the collection build and `ansible-galaxy collection install <tarball> --force` to test locally.```---## Change Types Supported| Change requested | Files to modify | How to handle ||-----------------|-----------------|---------------|| Bump version | galaxy.yml, CHANGELOG.md | Update version field; add CHANGELOG entry with date || Update description | galaxy.yml | Update description field || Add dependency | galaxy.yml | Append to dependencies dict with version range || Add role | roles/ | Create role dir using new-role logic; update galaxy.yml tags if needed || Add module | plugins/modules/<name>.py | Create complete module skeleton from `references/collection.md` || Add filter plugin | plugins/filter/<name>.py | Create FilterModule skeleton || Add lookup plugin | plugins/lookup/<name>.py | Create LookupBase skeleton || Update README | README.md | Apply requested textual change || Update meta/runtime.yml | meta/runtime.yml | Update requires_ansible or plugin_routing || Add CHANGELOG entry | CHANGELOG.md | Prepend new version entry |---## Version Bump Rules- **PATCH** bump (1.0.x → 1.0.x+1): bug fixes, no behavior changes- **MINOR** bump (1.x → 1.x+1.0): new features, backward-compatible- **MAJOR** bump (x → x+1.0.0): breaking changes — warn the user that this affects consumersWhen bumping version, always add a CHANGELOG entry:```markdown## [1.1.0] - 2026-03-31### Added- <description of what was added>### Changed- <description of what was changed>```

Frequently asked questions