duncanmcclean/bulk-changes
agents/skills/bulk-changes/SKILL.md
Makes the same change across multiple repositories.
$ install --global
skillsauthnpx skillsauth add duncanmcclean/dotfiles bulk-changesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 3:14 AM176.0s1 file scanned
SKILL.md
- name:
- bulk-changes
- description:
- Makes the same change across multiple repositories.
I am a Software Developer at Statamic. I maintain various open-source projects (first-party addons, first-party starter kits, and my own addons).
Even so often, I need to make a bulk change across all of the repositories. This skill is intended to help make that process easier.
1. Select the projects
There are three groups of projects I might want you to update:
- First-party addons
All located in
~/Code/Statamic.audit-log,collaboration,eloquent-driver,importer,migrator,podcast-categories,seo-pro,ssgandwikilinks - First-party starter kits
All located in
~/Code/Statamic. Repositories that start withstarter-kit- - My own addons
Most of which are located in
~/Code/SideProjects.cookie-notice,guest-entries,simple-commerce,statamic-cargoand~/Code/Statamic/Runway
When I execute this skill, you should ask me which group of projects to target.
2. Determine the task
Once the projects have been selected, you should ask me to specify the task. I may provide links to PRs or issues for reference or simply provide a bullet-point list of what needs to change.
3. Preview changes
Given information about the task, you should cd into the first project, checkout the default branch (whatever that is) and make the necessary changes.
Once complete, create a new branch, commit the changes (either as individual commits or as a single wip commit), push the changes to GitHub. From there, I will open a pull request and review the changes manually.
You should send me the link to create a pull request on GitHub for this repository. You should then present me with a few options using the ask_user_input_v0 tool:
- Question: "What would you like to do next?"
- Type:
single_select - Options: ["Continue", "Ask for Changes"]
Handle selections as follows:
-
"Continue" → continue onto step 4.
-
"Ask for Changes" → prompt the user: "What would you like to change?" then re-run this step with their feedback applied, and present the options again.
4. Copy changes
For each project:
- Checkout the default branch
- Make the necessary changes
- Don't just copy changes from the original project. Exact changes may differ between projects.
- Skip the remaining steps if no changes are necessary (eg. update has already been made manually, isn't required because dependency isn't present)
- Create a new branch using the same name as the first project
- Commit the changes (either as individual commits or as a single
wipcommit) and push the changes to GitHub. - Create a draft pull request using the
ghCLI.
- Please use the title and description from the original PR I created. DO NOT create your own titles and descriptions unless explicitly requested.
- Some projects include a version prefix in PR titles, eg.
[6.x]. You should fetch the latest PR to check if it contains a prefix before opening.
5. Result
Please respond with the following details for each project:
- Whether changes were made or the project was skipped
- Title of the pull request
- Link to the pull request
- Brief summary of changes made
From here, I may discuss failing tests or other changes needing made.
Related Skills
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026
steipete/xurl
tools
VerifiedTrustedCommunity
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
356,423SKILL.mdUpdated Apr 13, 2026