React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Add an Assisted-by: <agent-name/<model-id git trailer to commits made during an AI-assisted coding session.
Install Commit Assisted By
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fluxcd/agent-skills commit-assisted-by --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/skills/commit-assisted-by .claude/skills/commit-assisted-by && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .claude/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-byType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fluxcd/agent-skills commit-assisted-by --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/internal/skills/commit-assisted-by .agents/skills/commit-assisted-by && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .agents/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fluxcd/agent-skills commit-assisted-by --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/internal/skills/commit-assisted-by .cursor/skills/commit-assisted-by && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .cursor/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fluxcd/agent-skills.git --path internal/skills/commit-assisted-by--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fluxcd/agent-skills commit-assisted-by --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/internal/skills/commit-assisted-by .gemini/skills/commit-assisted-by && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .gemini/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fluxcd/agent-skills commit-assisted-byInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/internal/skills/commit-assisted-by .github/skills/commit-assisted-by && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .github/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fluxcd/agent-skills --skill commit-assisted-by -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fluxcd/agent-skills commit-assisted-by --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fluxcd/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/internal/skills/commit-assisted-by .opencode/skills/commit-assisted-by && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "commit-assisted-by" agent skill from https://github.com/fluxcd/agent-skills/tree/main/internal/skills/commit-assisted-by into .opencode/skills/commit-assisted-by/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-assisted-by", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
commit-assisted-by- GitHub stars
- 230
- Token cost
- ~1.3k tokens
- SKILL.md length
- 669 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Add an Assisted-by: <agent-name/<model-id git trailer to commits made during an AI-assisted coding session.
- Works in 3 steps: git log --oneline ..HEAD so the user can… → If is anything other than @{u}, run git… → If the range contains merge commits,…
- Any git commit activity visible in the session — either commits you make yourself
- SKILL.md covers Mode 1 — commits you create…, Mode 2 — commits that appear…, Mode 3 — explicit "tag the… and Anti-patterns
- Runs Shell scripts from its folder; calls git
What it does
Commit Assisted By is an agent skill from fluxcd/agent-skills. Add an Assisted-by: <agent-name/<model-id git trailer to commits made during an AI-assisted coding session. Trigger on any git commit activity visible in the session — either commits you make yourself, or commits the user makes outside your tool calls that surface in the conversation — even without an explicit request. Also trigger when the user explicitly asks to tag existing commits in a branch (e.g. "add assisted-by to commits in this branch").
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/safety-check.sh`).
It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: Skills to transform AI Agents into GitOps Engineers. The licence is Apache-2.0.
When your agent uses it
- Any git commit activity visible in the session — either commits you make yourself
- Commits the user makes outside your tool calls that surface in the conversation — even without an explicit request
- The user explicitly asks to tag existing commits in a branch (e.g
Example prompts
- “add assisted-by to commits in this branch”
- “/commit-assisted-by”
Requirements
- A Bash shell
- Pre-approved tools (allowed-tools): Bash(*/safety-check.sh), Bash(git commit:*), Bash(git log:*)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- git log --oneline ..HEAD so the user can see the commits that will be rewritten.
- If is anything other than @{u}, run git rev-list ..@{u} 2>/dev/null`. If non-empty, those
- If the range contains merge commits, stop and ask how to handle them. Default rebase linearizes merges
What it can do on your machine
Read from SKILL.md and the folder at commit 0d1fa6c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(*/safety-check.sh)Bash(git commit:*)Bash(git log:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Commit Assisted By loads about 1.3k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 669 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from fluxcd/agent-skills at commit 0d1fa6c, republished under its Apache-2.0 licence (© fluxcd). 669 words, ~1,329 tokens.
Download SKILL.mdSave it as
.claude/skills/commit-assisted-by/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- commit-assisted-by
- description
- Add an `Assisted-by: <agent-name>/<model-id>` git trailer to commits made during an AI-assisted coding session. Trigger on any `git commit` activity visible in the session — either commits you make yourself, or commits the user makes outside your tool calls that surface in the conversation — even without an explicit request. Also trigger when the user explicitly asks to tag existing commits in a branch (e.g. "add assisted-by to commits in this branch").
- allowed-tools
- Bash(*/safety-check.sh), Bash(git commit:*), Bash(git log:*)
- license
- Apache-2.0
Commit Assisted-by trailer
Record the assisting agent's involvement in a commit by adding an Assisted-by: <agent-name>/<model-id> git
trailer. The <agent-name> identify the specific AI assistant (CLI/harness) and <model-id> is the LLM version
that contributed to the commit. This disclosure provides transparency about AI involvement in code changes.
In the command examples below, substitute <agent-name>/<model-id> with your own values before running anything.
Mode 1 — commits you create yourself
When you create a commit in a session, limit the commit subject to 50 characters. Use the imperative mood in the subject line (e.g., "Add support for X" instead of "Added support for X").
If the commit message body is needed to explain what and why, wrap it at 72 characters. Avoid verbose explanations in the body, be as concise as possible while still conveying the necessary information.
Pass --trailer directly on the commit command. This is the clean path and avoids amend noise:
git commit -s -m "Add support for X" --trailer "Assisted-by: <agent-name>/<model-id>"Note that all commits must be signed off with a real human name and email to meet the DCO requirement. Never use your agent's name or a pseudonym in the sign-off or co-author fields.
Mode 2 — commits that appear outside your own git commit invocations
Sometimes a commit lands on HEAD that you did not run yourself — the user invoked git via a shell escape (e.g.
Claude Code's ! git commit ...) or a separate terminal. Your only window is after the fact.
Run the bundled safety-check script before amending. It prints safe, or skip:<reason> if HEAD is already
pushed, already trailered, a merge, or has a rebase/cherry-pick/revert/bisect in progress.
Invoke it with the script's full path — resolve scripts/safety-check.sh against the directory this SKILL.md was
loaded from, not the current working directory (the two are almost never the same):
<skill-dir>/scripts/safety-check.shOnly when the output is exactly safe, amend:
git commit --amend --no-edit --trailer "Assisted-by: <agent-name>/<model-id>"Follow up with one short line so the user knows the hash moved, e.g. "Amended HEAD to add Assisted-by trailer." If
the output starts with skip:, tell the user why the commit was skipped.
Mode 3 — explicit "tag the whole branch" request
Triggered by phrases like "add assisted-by to commits in this branch", "tag the commits on this branch", or "backfill the trailer". This is the only mode that rewrites more than HEAD, and only because the explicit request authorizes it. Never enter this mode on autopilot.
Show full SKILL.md (286 more words)Show less
Pick the base
Default to @{u} — it guarantees the range is only unpushed commits, which removes the force-push question
entirely. If the branch has no upstream, ask the user for an explicit base ref rather than guessing. If the user
names a base themselves ("from the last release tag"), honor it.
Show the plan, then confirm
git log --oneline <base>..HEADso the user can see the commits that will be rewritten.- If
<base>is anything other than@{u}, rungit rev-list <base>..@{u} 2>/dev/null. If non-empty, those commits are already on the remote — warn the user that after the rebase they will need to force-push to publish the rewrite, and confirm before proceeding. - If the range contains merge commits, stop and ask how to handle them. Default rebase linearizes merges
(destructive), and
--rebase-mergeswith--execon merges is fragile — not worth the risk without the user's judgment.
Run it
The exec short-circuits on commits that already carry the trailer, so the pass is idempotent:
git rebase <base> --exec 'git log -1 --format=%B | git interpret-trailers --parse | grep -qi "^Assisted-by:" || git commit --amend --no-edit --trailer "Assisted-by: <agent-name>/<model-id>"'Afterwards, report how many commits were tagged vs skipped. If the branch was already pushed, tell the user they
will need to run git push --force-with-lease themselves to publish the rewrite.
If the rebase hits a conflict, do not try to resolve it. Surface the conflict to the user and let them choose
--continue vs --abort.
Anti-patterns
- Never run
git pushyourself in any mode, even after a rebase. Publishing rewritten history is the user's call — surface the state and let them decide. - Don't use
Co-authored-by:— AI assistants are not GitHub users and the co-author convention is reserved for human collaborators.Assisted-by:is the correct semantic. - Don't fabricate or prettify either token. Use the actual agent/CLI/harness name and model ID/version.
© fluxcd, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in internal/skills/commit-assisted-by of fluxcd/agent-skills.
- SKILL.md
- scripts/safety-check.sh
Open the folder on GitHubat commit 0d1fa6c
Compare with similar skills
Commit Assisted By next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Commit Assisted By this skillfluxcd/agent-skills | 230 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
More from fluxcd/agent-skills
Gitops Repo Audit
fluxcd/agent-skills
Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated Flux APIs, reviews RBAC/multi-tenancy/secrets…
Gitops Knowledge
fluxcd/agent-skills
Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging).
Flux Controller Minor Releases
fluxcd/agent-skills
Run the upstream Flux controller minor release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller…
Flux Controller Patch Releases
fluxcd/agent-skills
Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller…
Gitops Cluster Debug
fluxcd/agent-skills
Debug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads controller logs, traces dependency chains, and…
Related
Works with
Categories
Questions about Commit Assisted By
What does Commit Assisted By do?
Add an Assisted-by: <agent-name/<model-id git trailer to commits made during an AI-assisted coding session. Commit Assisted By is an agent skill from fluxcd/agent-skills. Add an Assisted-by: <agent-name/<model-id git trailer to commits made during an AI-assisted coding session.
When should I use Commit Assisted By?
Commit Assisted By fits situations like: any git commit activity visible in the session — either commits you make yourself; commits the user makes outside your tool calls that surface in the conversation — even without an explicit request; the user explicitly asks to tag existing commits in a branch (e.g.
How do I install Commit Assisted By in Claude Code?
Run `npx skills add fluxcd/agent-skills --skill commit-assisted-by -a claude-code`. Or copy the skill folder (internal/skills/commit-assisted-by in fluxcd/agent-skills) into .claude/skills/commit-assisted-by in your project. Claude Code loads it when a task matches its description.
How do I install Commit Assisted By in Codex?
Run `npx skills add fluxcd/agent-skills --skill commit-assisted-by -a codex`. Or copy the skill folder (internal/skills/commit-assisted-by in fluxcd/agent-skills) into .agents/skills/commit-assisted-by in your project. Codex loads it when a task matches its description.
Can I use Commit Assisted By in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fluxcd/agent-skills --skill commit-assisted-by -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-assisted-by, .gemini/skills/commit-assisted-by, .github/skills/commit-assisted-by and .opencode/skills/commit-assisted-by in your project.
What does Commit Assisted By need to run?
Going by SKILL.md and its folder, Commit Assisted By needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash(*/safety-check.sh), Bash(git commit:*), Bash(git log:*).
Does Commit Assisted By access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Commit Assisted By safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Commit Assisted By use?
Commit Assisted By is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Commit Assisted By use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Commit Assisted By?
Skills that share tags, products or a category with Commit Assisted By: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commit Assisted By?
fluxcd (a GitHub organization) maintains it in fluxcd/agent-skills, which has 230 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 2, 2026.
Source: fluxcd/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.