Panel Review
stacklok/mecatl
Review completed non-trivial code across four independent axes: Spec, Standards, Test adequacy, and installed Domain specialists.
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea.
Install Code Changes
$ npx skills add JanDeDobbeleer/oh-my-posh --skill code-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JanDeDobbeleer/oh-my-posh code-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/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-changes .claude/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .claude/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-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 JanDeDobbeleer/oh-my-posh --skill code-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JanDeDobbeleer/oh-my-posh code-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/code-changes .agents/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .agents/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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 JanDeDobbeleer/oh-my-posh --skill code-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JanDeDobbeleer/oh-my-posh code-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/code-changes .cursor/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .cursor/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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/JanDeDobbeleer/oh-my-posh.git --path .agents/skills/code-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 JanDeDobbeleer/oh-my-posh --skill code-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JanDeDobbeleer/oh-my-posh code-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/code-changes .gemini/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .gemini/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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 JanDeDobbeleer/oh-my-posh code-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 JanDeDobbeleer/oh-my-posh --skill code-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/code-changes .github/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .github/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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 JanDeDobbeleer/oh-my-posh --skill code-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 JanDeDobbeleer/oh-my-posh code-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-posh.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/code-changes .opencode/skills/code-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 "code-changes" agent skill from https://github.com/JanDeDobbeleer/oh-my-posh/tree/main/.agents/skills/code-changes into .opencode/skills/code-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-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
code-changes- GitHub stars
- 24k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 527 words
- Files
- 12 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea.
- Works in 6 steps: Analyze (references/analyze.md) — root… → Plan (references/plan.md) — pinned spec,… → Delegate (references/delegate.md) —… → …
- Tasks that involve Refactoring
- SKILL.md covers Roles, The flow and Special cases
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Code Changes is an agent skill from JanDeDobbeleer/oh-my-posh. Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the right executor model, delegate and supervise subagents, verify, and deliver.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/analyze.md`, `references/artifacts.md` and `references/delegate.md`).
It sits in Development, covering Refactoring, Debugging and Pull requests. It works with Bash. The repository describes itself as: The most customisable and low-latency cross platform/shell prompt renderer. The licence is MIT.
When your agent uses it
- Tasks that involve Refactoring
- Tasks that involve Debugging
- Tasks that involve Pull requests
Example prompts
- “/code-changes”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Analyze (references/analyze.md) — root cause and scope, validated against the code,
- Plan (references/plan.md) — pinned spec, task split, parallel vs sequential, workspace per
- Delegate (references/delegate.md) — match each task to the right executor,
- Supervise (references/supervise.md) — monitor, unblock, and critically review
- Verify (references/verify.md) — quality gates plus functional proof, on the merged state,
- Deliver (references/deliver.md) — conventional commits and an outcome-first report.
What it can do on your machine
Read from SKILL.md and the folder at commit 1d6bd96. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Code Changes loads about 1.2k tokens when it runs, and up to ~9.8k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 527 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 JanDeDobbeleer/oh-my-posh at commit 1d6bd96, republished under its MIT licence (© JanDeDobbeleer). 527 words, ~1,166 tokens.
Download SKILL.mdSave it as
.claude/skills/code-changes/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- code-changes
- description
- Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the right executor model, delegate and supervise subagents, verify, and deliver.
Code Changes
The workflow for going from an issue, pull request, idea, or feature request to shipped code. Follow the phases in order. Analysis always comes first; code comes last.
Each phase has a reference file with the full instructions. Read the reference file when you enter the phase — not before, and never skip it because the phase "looks obvious". Every phase boundary carries a named artifact — see references/artifacts.md — so a phase can be re-entered later (a Verify failure, an escalation answer) without re-deriving context from scratch.
Roles
Assign work based on model capability. The coordinator is not the strongest model — it's the one that stays resident, owns every phase by default, and knows when it's out of its depth.
Role: Coordinator
- Capability tier: Capable mid-tier, resident for the whole task
- Owns: Analysis, plan, delegation, supervision, verification, delivery — by default
Role: Escalation
- Capability tier: Strongest reasoning model available; invoked only on trigger
- Owns: The specific judgment call the coordinator flagged, then control returns
Role: Implementer
- Capability tier: Same tier as coordinator, or smaller for trivial edits
- Owns: Executing one pinned, self-contained task
Role: Trivial
- Capability tier: Small, fast model for mechanical, unambiguous edits
- Owns: Batched renames, config tweaks, typo fixes, doc touch-ups — never judgment calls
Concrete model names per vendor (Anthropic, OpenAI, Google) and how to run the split in Claude Code, GitHub Copilot, Codex, or IDE agents: references/model-tiers.md.
When the current agent already runs at implementer tier, there's no separate delegation step for standard work: plan and execute directly, still following every phase. Escalate to the strongest model only when a trigger fires — see references/escalate.md — never by default and never for a routine judgment call the coordinator is equipped to make itself.
Show full SKILL.md (244 more words)Show less
The flow
- Analyze (references/analyze.md) — root cause and scope, validated against the code, never against the report alone.
- Plan (references/plan.md) — pinned spec, task split, parallel vs sequential, workspace per task.
- Delegate (references/delegate.md) — match each task to the right executor, coordinator-tier by default.
- Supervise (references/supervise.md) — monitor, unblock, and critically review implementer output.
- Verify (references/verify.md) — quality gates plus functional proof, on the merged state, never delegated downward. A second consecutive failed cycle escalates instead of looping a third time.
- Deliver (references/deliver.md) — conventional commits and an outcome-first report.
Analyze, Supervise, and Verify each carry an escalation checkpoint — see references/escalate.md — for handing one specific judgment call to the strongest available model without giving up ownership of the phase.
Stop gate: Phase 1 ends with reporting the analysis and proposed approach to the user and waiting for a go. Skip the gate only when the user already gave the go in the request itself ("do it", "fix it and commit", "implement with Sonnet").
Special cases
These are alternate Phase 1 entry points, not a separate track: each one must still produce the same analysis-report artifact defined in references/artifacts.md, so Plan can consume it without knowing which door the task came in through. The rest of the flow (Phases 2–6) applies unchanged. Use references/analyze.md directly whenever the request already implies a fix (its opening section states the exact predicate); reserve these two for their narrower deliverable:
- Pull request review comments → references/pr-review-comments.md
- Issue triage → references/issue-triage.md
© JanDeDobbeleer, MIT. 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 11 other files (references) in .agents/skills/code-changes of JanDeDobbeleer/oh-my-posh.
- SKILL.md
- references/analyze.md
- references/artifacts.md
- references/delegate.md
- references/deliver.md
- references/escalate.md
- references/issue-triage.md
- references/model-tiers.md
- references/plan.md
- references/pr-review-comments.md
- references/supervise.md
- references/verify.md
Open the folder on GitHubat commit 1d6bd96
Compare with similar skills
Code 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 |
|---|---|---|---|---|---|---|
| Code Changes this skillJanDeDobbeleer/oh-my-posh | 24k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Panel Reviewstacklok/mecatl | 218 | — | ~5.8k | Automated safety check: Pass | Apache-2.0 | |
| Julessanjay3290/ai-skills | 430 | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Coding AgentTermiX-official/cryptoclaw | 100 | 8 repos | ~2.7k | Automated safety check: Pass | MIT | |
| FIXME Resolvertailcallhq/forgecode | 7.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Jules
sanjay3290/ai-skills
Delegate coding tasks to Google Jules AI agent for asynchronous execution.
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Coding Agent
TermiX-official/cryptoclaw
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process.
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
More from JanDeDobbeleer/oh-my-posh
All 11 skills in this repoSegment Docs
JanDeDobbeleer/oh-my-posh
Reference mapping between Oh My Posh Go segment source code and MDX documentation.
Segment Create
JanDeDobbeleer/oh-my-posh
Full scaffolding workflow for creating a new Oh My Posh segment.
Architecture
JanDeDobbeleer/oh-my-posh
Cross-language architecture and clean-code principles for this project: Clean Code, Object Calisthenics, SOLID, guard clauses, hot-path cost, and the code review checklist.
Conventional Commit
JanDeDobbeleer/oh-my-posh
Workflow for generating conventional commit messages following the Conventional Commits specification.
Golang
JanDeDobbeleer/oh-my-posh
Go coding standards and conventions for this project. An agent skill from JanDeDobbeleer/oh-my-posh.
Markdown
JanDeDobbeleer/oh-my-posh
Markdown formatting rules for this project. An agent skill from JanDeDobbeleer/oh-my-posh.
Related
Works with
Categories
Questions about Code Changes
What does Code Changes do?
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. Code Changes is an agent skill from JanDeDobbeleer/oh-my-posh. Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea.
When should I use Code Changes?
Code Changes fits situations like: tasks that involve Refactoring; tasks that involve Debugging; tasks that involve Pull requests.
How do I install Code Changes in Claude Code?
Run `npx skills add JanDeDobbeleer/oh-my-posh --skill code-changes -a claude-code`. Or copy the skill folder (.agents/skills/code-changes in JanDeDobbeleer/oh-my-posh) into .claude/skills/code-changes in your project. Claude Code loads it when a task matches its description.
How do I install Code Changes in Codex?
Run `npx skills add JanDeDobbeleer/oh-my-posh --skill code-changes -a codex`. Or copy the skill folder (.agents/skills/code-changes in JanDeDobbeleer/oh-my-posh) into .agents/skills/code-changes in your project. Codex loads it when a task matches its description.
Can I use Code 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 JanDeDobbeleer/oh-my-posh --skill code-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/code-changes, .gemini/skills/code-changes, .github/skills/code-changes and .opencode/skills/code-changes in your project.
What does Code Changes need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Changes is instructions for the agent only.
Does Code 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 Code 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 Code Changes use?
Code Changes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Changes use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.6k tokens, read only when the agent opens those files.
What are the alternatives to Code Changes?
Skills that share tags, products or a category with Code Changes: Panel Review (stacklok/mecatl, 218 stars), Jules (sanjay3290/ai-skills, 430 stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Coding Agent (TermiX-official/cryptoclaw, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Changes?
JanDeDobbeleer (a GitHub user) maintains it in JanDeDobbeleer/oh-my-posh, which has 23,555 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: JanDeDobbeleer/oh-my-posh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.