PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
Required before you commit, push or open a pull request here, asked or not.
Install Commit Changes
$ npx skills add epam/cloud-pipeline --skill commit-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/cloud-pipeline commit-changes --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/epam/cloud-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-changes .claude/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .claude/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changesType 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 epam/cloud-pipeline --skill commit-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/cloud-pipeline commit-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/commit-changes .agents/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .agents/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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 epam/cloud-pipeline --skill commit-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/cloud-pipeline commit-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/commit-changes .cursor/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .cursor/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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/epam/cloud-pipeline.git --path .agents/skills/commit-changes--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 epam/cloud-pipeline --skill commit-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/cloud-pipeline commit-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/commit-changes .gemini/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .gemini/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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 epam/cloud-pipeline commit-changesInstalls 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 epam/cloud-pipeline --skill commit-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/commit-changes .github/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .github/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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 epam/cloud-pipeline --skill commit-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install epam/cloud-pipeline commit-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/commit-changes .opencode/skills/commit-changes && 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-changes" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/commit-changes into .opencode/skills/commit-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-changes", 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-changes- GitHub stars
- 162
- Token cost
- ~1.3k tokens
- SKILL.md length
- 730 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Required before you commit, push or open a pull request here, asked or not.
- Works in 6 steps: What you are authorized to do → Preconditions → Commit message → …
- Tasks that involve Commit messages
- SKILL.md covers 1. What you are authorized to do, 2. Preconditions, 3. Commit message and 4. Push, plus 2 more sections
- Calls claude
What it does
Commit Changes is an agent skill from epam/cloud-pipeline. Required before you commit, push or open a pull request here, asked or not. Holds the preconditions, the subject line and its trailers, the draft PR, and the issue label afterward.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages and Pull requests. The repository describes itself as: Cloud agnostic genomics analysis, scientific computation and storage platform. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Pull requests
Example prompts
- “/commit-changes”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5017688. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Changes loads about 1.3k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 730 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from epam/cloud-pipeline at commit 5017688, republished under its Apache-2.0 licence (© epam). 730 words, ~1,325 tokens.
Download SKILL.mdSave it as
.claude/skills/commit-changes/SKILL.md (or your agent's skills folder).- name
- commit-changes
- description
- Required before you commit, push or open a pull request here, asked or not. Holds the preconditions, the subject line and its trailers, the draft PR, and the issue label afterward.
Committing changes
The Publish step. The change is finished, checked and reviewed — §2 is how you confirm that.
1. What you are authorized to do
Unattended when you cannot get an answer before the next step (see the implement-task skill).
| Step | Attended | Unattended |
|---|---|---|
| commit | only when asked | authorized by the task trigger |
| push | a separate instruction | same trigger |
Attended: stop after the step you were asked for. "Commit this" is not permission to push. Infer nothing.
Unattended: one trigger carries both. Stopping to be asked produces nothing a reviewer can see — the instruction already arrived.
2. Preconditions
- Not on a shared branch.
develop— matched exactly, sodevelop-xxxxis fine — plusrelease/*andstage/*. If that isHEAD, stop — theimplement-taskskill → "Workspace" has the rule. - You have read your own diff, and an agent that did not write it has reviewed it. The Diff review
step — the
implement-taskskill → "Fresh-eyes review". - Checks ran, and passed. The
verify-changesskill is how you work out which ones you owe. A change whose checks failed is reported as blocked, not committed. - The tests the change owes are in the diff — the
implement-taskskill → "Tests". Changed code owes one as much as new code does; a missing runner is stated, not treated as an exemption. - If the diff touches instruction files — any
AGENTS.md,CLAUDE.md,.claude/,.cursor/,.github/instructions/,.agents/— the instruction verifier has run and passed:bash .agents/skills/modifying-instructions/scripts/verify-instructions.sh - The docs the change owes are in the diff — the
implement-taskskill → "Docs", andCONTRIBUTIONS.md→ "Documenting" behind it. A user-visible change with no documentation commit is not finished.
3. Commit message
Keep it short — a subject line and the trailer, a few lines at most. Skip the bullet list of what changed: the diff says that, and the PR body is where the explanation belongs.
Reference the issue; both forms are in current use:
Issue 4538 remove hardcoded notification timestamp fields in favor of timestamp tags
Issue #4461: Introduce Platform Usage Credits to optimize costs - non-admin fixesThe number is in the branch name already, so take it from there rather than deriving it again.
Genuinely no issue (small infrastructure, scripts) is a plain descriptive subject with no number,
matching the feature/ or fix/ branch it sits on — a conclusion Intake reached with whoever asked,
not one to reach here for the first time. Not knowing the number of an issue that exists is a different
thing, and the implement-task skill → "Issue number" has what to do about it.
Do not append a pull request number like (#4545) to the subject.
Every agent-authored commit ends with this trailer, on its own line after a blank line:
Co-authored-by: Cloud Pipeline Agent (<model>) <noreply@epam.com><model> is what wrote the change — Claude Opus 5, Claude Sonnet 4.6, Cursor, Codex. This
replaces your harness default — emit this line instead of your own, not both. Human commits carry
no trailer.
Show full SKILL.md (283 more words)Show less
4. Push
Never force-push — not a shared branch, not your own, no exceptions.
Falling behind the base by itself needs nothing — only an actual conflict, or an explicit need for something newer on it, is a reason to reconcile, and merging the base in is how you do that.
5. Open the pull request
Same authorization split as commit and push: attended, a separate instruction; unattended, the same
trigger carries it through. Always --draft, never plain. Marking it ready is the author's call
and needs its own instruction; unattended it stays a draft. If the branch already has an open PR, push
more commits to it instead of running this again.
Label it intel/artificial 🤖 — CONTRIBUTIONS.md → "Authorship labels". One that already exists
gets the label just the same, whoever opened it.
Body follows .github/pull_request_template.md — nothing applies it for you, so open that file and
fill its shape in rather than inventing one.
6. Hand back
Which step you did, and the one you stopped before — attended that is the next instruction someone
owes you, so leaving it implicit reads as failure rather than the next step. Plus the commit subject,
the branch, and the base it was cut from, since whoever opens the pull request needs the base and
cannot infer it from the branch, plus intel/artificial 🤖 for the pull request they open.
Then Aftercare, once the change is pushed: add intel/artificial 🤖 to the issue, plus state/has-doc
if the diff added docs, and state/has-case / state/has-e2e only if it added those. Leave
intel/natural 🧐 alone where the issue carries it — CONTRIBUTIONS.md → "Authorship labels". Never
set state/verify or state/ready. Attended, confirm first; unattended, do it as part of the same
trigger and say so in the hand-back.
© epam, 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
Just SKILL.md in .agents/skills/commit-changes of epam/cloud-pipeline.
Open the folder on GitHubat commit 5017688
Compare with similar skills
Commit Changes 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 Changes this skillepam/cloud-pipeline | 162 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| 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 | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
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.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
More from epam/cloud-pipeline
All 8 skills in this repoVerify Client Live
epam/cloud-pipeline
Open a user-visible client/ change in a browser against a real Cloud Pipeline deployment.
Configure Dev Environment
epam/cloud-pipeline
Learn which toolchains and environments this workstation has and how to invoke them, or set them up when they are missing.
Modifying Instructions
epam/cloud-pipeline
Required before adding or changing anything an agent reads — a convention in AGENTS.md, a procedure as a skill, a pattern-scoped rule.
Plan Change
epam/cloud-pipeline
Plan the work before you edit — its phases, the model and effort each takes, and whether it is worth a plan file with a ledger beside it.
Verify Changes
epam/cloud-pipeline
Find and run the checks a change owes, from what it touches and what that can reach.
Implement Task
epam/cloud-pipeline
Start here before the first edit of any file — a one-liner and a docs change included.
Related
Categories
Questions about Commit Changes
What does Commit Changes do?
Required before you commit, push or open a pull request here, asked or not. Commit Changes is an agent skill from epam/cloud-pipeline. Required before you commit, push or open a pull request here, asked or not.
When should I use Commit Changes?
Commit Changes fits situations like: tasks that involve Commit messages; tasks that involve Pull requests.
How do I install Commit Changes in Claude Code?
Run `npx skills add epam/cloud-pipeline --skill commit-changes -a claude-code`. Or copy the skill folder (.agents/skills/commit-changes in epam/cloud-pipeline) into .claude/skills/commit-changes in your project. Claude Code loads it when a task matches its description.
How do I install Commit Changes in Codex?
Run `npx skills add epam/cloud-pipeline --skill commit-changes -a codex`. Or copy the skill folder (.agents/skills/commit-changes in epam/cloud-pipeline) into .agents/skills/commit-changes in your project. Codex loads it when a task matches its description.
Can I use Commit Changes 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 epam/cloud-pipeline --skill commit-changes -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-changes, .gemini/skills/commit-changes, .github/skills/commit-changes and .opencode/skills/commit-changes in your project.
What does Commit Changes need to run?
Going by SKILL.md and its folder, Commit Changes needs the command-line tools its instructions call (claude).
Does Commit Changes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Commit Changes 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. Review the folder before installing.
What licence does Commit Changes use?
Commit Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Commit Changes 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 Changes?
Skills that share tags, products or a category with Commit Changes: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commit Changes?
epam (a GitHub organization) maintains it in epam/cloud-pipeline, which has 162 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.
Source: epam/cloud-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.