omcustomcodex:auto-improve
Automates the application of improvement suggestions to project configurations.
Install
mkdir -p .claude/skills/omcustomcodex-auto-improve && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18810" && unzip -o skill.zip -d .claude/skills/omcustomcodex-auto-improve && rm skill.zipInstalls to .claude/skills/omcustomcodex-auto-improve
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Apply verified improvement suggestions from eval-core analysis to omcodex configurationKey capabilities
- →Read improvement suggestions from eval-core analysis
- →Allow user selection of suggestions to apply
- →Apply changes in an isolated worktree
- →Verify changes with sauron
- →Create a pull request for review
- →Transition item status from `proposed` to `approved` and `applied`
How it works
The skill reads improvement suggestions from eval-core, allows user selection, applies changes in an isolated worktree, verifies them with sauron, and creates a pull request, managing the status transitions of the suggestions.
Inputs & outputs
When to use omcustomcodex:auto-improve
- →Apply improvement suggestions
- →Automate configuration updates
About this skill
/omcustomcodex:auto-improve — Automated Improvement Workflow
Purpose
Reads improvement suggestions from eval-core analysis, lets the user select which to apply, applies changes in an isolated worktree with sauron verification, and creates a PR for review.
Usage
/omcustomcodex:auto-improve # Interactive selection from pending suggestions
Prerequisites
- eval-core analysis data exists (run
/omcustomcodex:improve-reportfirst if empty) - Pending improvement suggestions in
proposedstatus
Workflow
Step 1: Read Suggestions
- Run
bun run packages/eval-core/src/cli/index.ts analyze --format json --savevia Bash - Parse JSON output for improvement suggestions
- If no suggestions: display "No improvement suggestions available" and exit
Step 2: Display & Select
Display numbered list:
[Auto-Improve] Available suggestions:
1. [HIGH] agent:lang-golang-expert — Escalate model frontier/medium→frontier/high (3 failures in 5 uses)
2. [MED] routing:dev-lead-routing — Add Flutter keyword mapping (2 routing misses)
3. [LOW] skill:systematic-debugging — Add timeout guard (1 timeout in 10 uses)
Select items: [1,2,3] / "all" / "cancel"
Self-reference filter: Exclude items where targetName matches:
omcodex:auto-improve,auto-improvepipeline-guards,evaluator-optimizer- Any item targeting this skill itself
Step 3: Approve (State Transition)
For each selected item:
- Call eval-core API: transition
proposed→approved - Display:
[Approved] {N} items selected for application
Step 4: Worktree Isolation
- Use
EnterWorktreetool with nameauto-improve-{YYYYMMDD} - Creates isolated branch from HEAD
Step 5: Apply Changes
Map each approved item to the appropriate subagent by targetType:
| targetType | Agent | Action |
|---|---|---|
| agent | mgr-creator | Modify agent frontmatter/body |
| skill | mgr-creator | Revise skill SKILL.md (R010 Protected Paths) |
| routing | mgr-creator | Update routing patterns (R010 Protected Paths) |
| model-escalation | general-purpose | Update model field in agent frontmatter |
Spawn agents in parallel (max 4 per R009). Each agent receives:
- Action description and evidence data
- Target file path
- Specific modification instructions
Step 6: Verification
- Delegate to mgr-sauron: full R017 verification
- If PASS: proceed to Step 7
- If FAIL: display failures, offer options:
fix→ re-apply with sauron feedback (max 2 cycles)reject→ transition all torejected, ExitWorktree(remove)manual→ keep worktree for user inspection
Step 7: PR & Finalize
- Delegate to mgr-gitnerd: commit + create PR
- Title:
chore(auto-improve): apply {N} improvement suggestions - Body: table of applied items with evidence
- Title:
- Transition all items to
appliedwithappliedAttimestamp and PR URL ExitWorktree(action: "keep")— keep branch for PR- Display PR URL to user
Safety Guards
| Guard | Implementation |
|---|---|
| Self-reference prevention | Blocklist filter in Step 2 |
| User approval gate | Step 2 interactive selection |
| Worktree isolation | Step 4 EnterWorktree |
| Sauron verification | Step 6 mandatory pass |
| PR-based merge | Step 7 — no direct push to develop |
| Max items per run | 20 default, 50 hard cap |
| Max fix cycles | 2 retries before rejection |
| Rollback | git revert via mgr-gitnerd post-merge |
Error Handling
| Scenario | Action |
|---|---|
| No suggestions available | Display message, exit |
| User cancels selection | Exit, no state changes |
| Sauron verification fails 2x | Reject all, cleanup worktree |
| Agent application error | Mark individual item as rejected, continue others |
| EnterWorktree fails | Report error, exit |
Display Format
[Auto-Improve] Starting improvement workflow
├── Suggestions: {N} available ({high}H/{medium}M/{low}L confidence)
├── Self-reference filtered: {count} items excluded
└── Select items to apply: [1,2,3] or "all" or "cancel"
[Auto-Improve] Applying {N} improvements in worktree
├── Worktree: auto-improve-{date}
├── Agents: {count} parallel
└── Pipeline guards: max 20 items, 2 retry cycles
[Auto-Improve] Verification
├── Sauron: {PASS|FAIL}
├── PR: #{number} created
└── Status: {N} items → applied
When not to use it
- →If eval-core analysis data does not exist
- →If there are no pending improvement suggestions
- →To directly push to the develop branch
Limitations
- →Requires eval-core analysis data to exist
- →Requires pending improvement suggestions in `proposed` status
- →No direct push to develop
How it compares
This skill automates the application and verification of improvement suggestions from an analysis tool in a controlled worktree environment, ensuring a structured and auditable process for code changes, unlike manual application.
Compared to similar skills
omcustomcodex:auto-improve side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| omcustomcodex:auto-improve (this skill) | 0 | 14d | No flags | Advanced |
| command-development | 16 | 8mo | Review | Intermediate |
| skill-forge | 11 | 8mo | Review | Intermediate |
| codex-skill | 12 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by baekenough
View all by baekenough →You might also like
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
peekaboo
openclaw
Capture and automate macOS UI with the Peekaboo CLI.