New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Speckit Review Simplify

by opsmill in opsmill/infrahub

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions.

Apache-2.0Auto-check passedDevelopment

Install Speckit Review Simplify

skills CLI
$ npx skills add opsmill/infrahub --skill speckit-review-simplify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install opsmill/infrahub speckit-review-simplify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/speckit-review-simplify .claude/skills/speckit-review-simplify && rm -rf skills-src

Use ~/.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/

Facts

Skill name
speckit-review-simplify
GitHub stars
533
Used in
1 other repo
Token cost
~1k tokens
SKILL.md length
508 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions.

  • Works in 5 steps: Preserve Functionality: Never change… → Apply Project Standards: Follow the… → Enhance Clarity: Simplify code structure… → …
  • Tasks that involve Spec-driven development
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Code simplification

What it does

Speckit Review Simplify is an agent skill from opsmill/infrahub. Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory

It sits in Development, covering Spec-driven development and Code simplification. The repository describes itself as: Infrahub is a graph-based data management platform with built-in version control, CI workflows, peer review, and API access. It’s purpose-built to power reliable infrastructure… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Spec-driven development
  • Tasks that involve Code simplification

Example prompts

  • “/speckit-review-simplify”

Requirements

  • Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Preserve Functionality: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain…
  2. Apply Project Standards: Follow the established coding standards from project guidelines (typically in .specify/memory/constitution.md…
  3. Enhance Clarity: Simplify code structure by
  4. Maintain Balance: Avoid over-simplification that could
  5. Focus Scope: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a…

What it can do on your machine

Read from SKILL.md and the folder at commit 2e1f1eb. 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.

  • Compatibility

    Requires spec-kit project structure with .specify/ directory

    From compatibility in the SKILL.md frontmatter.

Context cost

Speckit Review Simplify loads about 1k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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 opsmill/infrahub at commit 2e1f1eb, republished under its Apache-2.0 licence (© opsmill). 508 words, ~1,035 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-review-simplify/SKILL.md (or your agent's skills folder).
name
speckit-review-simplify
description
Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
github-spec-kit
metadata.source
review:commands/simplify.md

You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions. This is a balance that you have mastered as a result your years as an expert software engineer.

Determine Changed Files:

If the user provided a file list or explicit instructions on how to retrieve files (e.g., only staged, only unstaged, a specific folder, etc.), follow those instructions directly.

Otherwise, you MUST execute the .specify/scripts/bash/detect-changed-files.sh with --json to detect changed files. Do not attempt to detect changes by running git commands directly, reading git state manually, or using any other method — always delegate to the script. The script automatically picks the best detection mode:

  • Mode A (feature branch): diffs the current branch against the default branch (main/master) from the merge-base, plus any staged and unstaged changes.
  • Mode B (working directory): falls back to staged + unstaged changes when there is no feature branch (e.g., working directly on the default branch).

JSON output: {"branch", "default_branch", "mode", "changed_files": [...]}

Note: The folder containing the script may be excluded from version control or hidden by search indexing. You must still locate and execute it — do not skip it or substitute your own file-detection logic.

Simplify Framework:

You will analyze recently modified code and apply refinements that:

  1. Preserve Functionality: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.

  2. Apply Project Standards: Follow the established coding standards from project guidelines (typically in .specify/memory/constitution.md, CLAUDE.md, .github/copilot-instructions.md or equivalent).

  3. Enhance Clarity: Simplify code structure by:

    • Reducing unnecessary complexity and nesting
    • Eliminating redundant code and abstractions
    • Improving readability through clear variable and function names
    • Consolidating related logic
    • Removing unnecessary comments that describe obvious code
    • IMPORTANT: Avoid nested ternary operators - prefer switch statements or if/else chains for multiple conditions
    • Choose clarity over brevity - explicit code is often better than overly compact code

  4. Maintain Balance: Avoid over-simplification that could:

    • Reduce code clarity or maintainability
    • Create overly clever solutions that are hard to understand
    • Combine too many concerns into single functions or components
    • Remove helpful abstractions that improve code organization
    • Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
    • Make the code harder to debug or extend

  5. Focus Scope: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.

Show full SKILL.md (88 more words)Show less

Your refinement process:

  1. Identify the recently modified code sections
  2. Analyze for opportunities to improve elegance and consistency
  3. Apply project-specific best practices and coding standards
  4. Ensure all functionality remains unchanged
  5. Verify the refined code is simpler and more maintainable
  6. Document only significant changes that affect understanding

You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.

© opsmill, 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/speckit-review-simplify of opsmill/infrahub.

Open the folder on GitHubat commit 2e1f1eb

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in opsmill/infrahub, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Speckit Review Simplify 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.

Speckit Review Simplify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Review Simplify this skillopsmill/infrahub5331 repos~1kAutomated safety check: PassApache-2.0
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec71k2 repos~5.6kAutomated safety check: PassMIT
PonytailDavidObando/gsharp5648 repos~1.7kAutomated safety check: PassMIT
Ponytail Reviewkortix-ai/suna20k4 repos~593Automated safety check: PassCustom licence
Speckit ConstitutionWeihanLi/WeihanLi.Common24211 repos~2.1kAutomated safety check: PassApache-2.0
Ponytail Lazy Developer ModeDietrichGebert/ponytail159k—~873Automated safety check: PassMIT

Similar skills

  • OpenSpec Bulk Change Archiver

    Fission-AI/OpenSpec

    Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    71k GitHub starsUsed in 2 repos~5.6k tokens
    DevelopmentAuto-check passed

  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    564 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Ponytail Review

    kortix-ai/suna

    Code review focused exclusively on over-engineering. An agent skill from kortix-ai/suna.

    20k GitHub starsUsed in 4 repos~593 tokens
    DevelopmentAuto-check passed

  • Speckit Constitution

    WeihanLi/WeihanLi.Common

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

    242 GitHub starsUsed in 11 repos~2.1k tokens
    DevelopmentAuto-check passed

  • Ponytail Lazy Developer Mode

    DietrichGebert/ponytail

    Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.

    159k GitHub stars~873 tokensUpdated today
    DevelopmentAuto-check passed

  • Code Simplification for ego-lite

    citrolabs/ego-lite

    Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.

    17k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from opsmill/infrahub

All 32 skills in this repo

  • Analyzing CI Flakiness

    opsmill/infrahub

    Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal…

    533 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Audit Docs

    opsmill/infrahub

    Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers…

    533 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Commit

    opsmill/infrahub

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream.

    533 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

  • Creating Changelog Entries

    opsmill/infrahub

    A skill your agent uses when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or…

    533 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Creating Issues

    opsmill/infrahub

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

    533 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Creating Prd

    opsmill/infrahub

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue).

    533 GitHub stars~4k tokensUpdated today
    Auto-check passed

Categories

Questions about Speckit Review Simplify

What does Speckit Review Simplify do?

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Speckit Review Simplify is an agent skill from opsmill/infrahub. Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions.

When should I use Speckit Review Simplify?

Speckit Review Simplify fits situations like: tasks that involve Spec-driven development; tasks that involve Code simplification.

How do I install Speckit Review Simplify in Claude Code?

Run `npx skills add opsmill/infrahub --skill speckit-review-simplify -a claude-code`. Or copy the skill folder (.agents/skills/speckit-review-simplify in opsmill/infrahub) into .claude/skills/speckit-review-simplify in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Review Simplify in Codex?

Run `npx skills add opsmill/infrahub --skill speckit-review-simplify -a codex`. Or copy the skill folder (.agents/skills/speckit-review-simplify in opsmill/infrahub) into .agents/skills/speckit-review-simplify in your project. Codex loads it when a task matches its description.

Can I use Speckit Review Simplify 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 opsmill/infrahub --skill speckit-review-simplify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-review-simplify, .gemini/skills/speckit-review-simplify, .github/skills/speckit-review-simplify and .opencode/skills/speckit-review-simplify in your project.

What does Speckit Review Simplify need to run?

SKILL.md names no scripts, command-line tools or credentials: Speckit Review Simplify is instructions for the agent only. Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Review Simplify 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 Speckit Review Simplify 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 Speckit Review Simplify use?

Speckit Review Simplify 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 Speckit Review Simplify use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Speckit Review Simplify?

Skills that share tags, products or a category with Speckit Review Simplify: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Ponytail (DavidObando/gsharp, 564 stars), Ponytail Review (kortix-ai/suna, 20k stars) and Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Review Simplify?

opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 533 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 9, 2026.

Source: opsmill/infrahub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.