git-xargs CLI
The CLI runs a chosen script across GitHub repositories, commits the changes and opens pull requests for review.
- 1,137 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The CLI automatically runs a supplied arbitrary script, commits files and pushes changes to repositories accessible through the token.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/git-xargsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The CLI automatically runs a supplied arbitrary script, commits files and pushes changes to repositories accessible through the token.
This is third-party code. Review the repository files before installing.
What it does
git-xargs accepts repositories and one command or script. It clones each project, runs the task, commits changed files and opens a pull request. An agent can prepare a shared configuration update for review repository by repository. Targets can come from an organization, a file, arguments or standard input. The final report records changes and errors, and small batches help validate a script before wider use.
Who it is for. Maintainers of many GitHub repositories applying one configuration change through separate pull requests.
Good fit when
- A team is updating a shared CI file across its repositories.
- An agent has prepared a tested replacement after a product rename.
- Several projects need the same approved maintenance file.
- Before pushing changes to GitHub, the team wants a report from a pilot batch.
Not a fit when
- The script has not been tested on one local repository.
- Each repository needs an individually designed edit.
- The supplied command must not run with local user permissions.
Example request
Prepare a CI update script for three authorized repositories and first run a pilot without pushing changes.Limitations
The `--dry-run` option prevents pushes and pull requests through GitHub, but the script still runs locally. All new and modified files in the clone are staged, so the script should leave only intended changes. Supply `--branch-name`; a base-branch override applies to every selected repository. GitHub request limits can slow large batches, requiring a longer interval between pull requests rather than unrestricted parallel API calls.
How to disable. Stop the git-xargs process. Review and undo existing branches, commits and pull requests separately.
FAQ
Does a dry run change files?
Yes, the script runs in local clones. `--dry-run` prevents remote pushes and pull requests.
How do I target one repository?
Use `--repo`, repeating it for additional projects.
Which branch receives a pull request?
The repository default branch, unless `--base-branch-name` overrides it.
Why did CI not start?
Commit messages receive `[skip ci]` by default. Use `--no-skip-ci` when CI should run.
Which files are committed?
All new and modified files in the clone; check script output before a broad run.
Discussion
No questions or reviews yet.
Related
CLI toolsThe terminal GitHub dashboard shows issues and pull requests so users can review agent work in configurable sections.
The gix and ein CLIs expose repository inspection and selected operations built on a Rust implementation of Git.
A CLI that opens a local git diff in the browser like GitHub's Files changed tab; comments copy out as prompts for an agent
The GitHub CLI extension gh stack and an agent skill: a chain of dependent branches and PRs with rebase, submit and merge of the whole stack
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
A Go tool for GitHub issues: Markdown files on disk that an agent edits in bulk and the push command sends back.
README in short
GitHub Enterprise host configuration, reviewer assignment and draft pull requests are supported.