New: 97,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

Review Cross Command Consistency

by ruby-git in ruby-git/ruby-git

Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture.

MITAuto-check passed

Install Review Cross Command Consistency

skills CLI
$ npx skills add ruby-git/ruby-git --skill review-cross-command-consistency -a claude-code

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

GitHub CLI
$ gh skill install ruby-git/ruby-git review-cross-command-consistency --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/ruby-git/ruby-git.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/review-cross-command-consistency .claude/skills/review-cross-command-consistency && 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
review-cross-command-consistency
GitHub stars
1.8k
Token cost
~1.6k tokens
SKILL.md length
633 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture.

  • Works in 7 steps: Class structure consistency → Arguments DSL consistency → Exit-status consistency → …
  • Cross-command audits
  • SKILL.md covers Contents, How to use this skill, Prerequisites and Related skills, plus 3 more sections
  • Calls git

What it does

Review Cross Command Consistency is an agent skill from ruby-git/ruby-git. Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture. Use for cross-command audits.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Ruby/Git is a Ruby library that can be used to create, read and manipulate Git repositories by wrapping system calls to the git binary. The licence is MIT.

When your agent uses it

  • Cross-command audits

Example prompts

  • “Use the review-cross-command-consistency skill to compare sibling command classes for consistent structure, documentation, testing, and exit-status…”
  • “/review-cross-command-consistency”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Class structure consistency
  2. Arguments DSL consistency
  3. Exit-status consistency
  4. YARD consistency
  5. Unit spec consistency
  6. Integration spec consistency
  7. Migration process consistency

What it can do on your machine

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

    • 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

Review Cross Command Consistency loads about 1.6k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 633 words of instructions outside code blocks.

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

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 ruby-git/ruby-git at commit f3bf20f, republished under its MIT licence (© ruby-git). 633 words, ~1,581 tokens.

Download SKILL.mdSave it as .claude/skills/review-cross-command-consistency/SKILL.md (or your agent's skills folder).
name
review-cross-command-consistency
description
Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture. Use for cross-command audits.

Review Cross-Command Consistency

Review sibling command classes (same module/family) for consistent structure, documentation, testing, and exit-status conventions under the Base architecture.

Contents

How to use this skill

Attach this file to your Copilot Chat context, then invoke it with the sibling command files (same module/family) to compare. Examples:

text
Using the Review Cross-Command Consistency skill, review the
Git::Commands::Diff family: lib/git/commands/diff/patch.rb,
lib/git/commands/diff/numstat.rb, lib/git/commands/diff/raw.rb.
text
Review Cross-Command Consistency: all files under lib/git/commands/stash/

The invocation needs two or more sibling command files from the same family.

Prerequisites

Before starting, you MUST load the following skill(s) in their entirety:

  • YARD Documentation — authoritative source for YARD formatting rules and writing standards;

Version-Aware Comparison Scope

Before flagging siblings as inconsistent for option names, aliases, negated forms, or documented values, determine the repository's minimum supported Git version from project metadata. In this repository, git.gemspec declares git 2.43.0 or greater.

Consistency judgments for CLI surface area must be based on the minimum supported Git version, not only on the locally installed Git. Use version-matched upstream documentation first, version-matched upstream source when exact parser behavior is ambiguous, and local git <command> -h output only as a supplemental check.

What to Check

1. Class structure consistency
  • all classes use class < Git::Commands::Base
  • all require git/commands/base
  • all use arguments do ... end (no legacy ARGS = constants)
  • simple commands carry YARD directive # @!method call(*, **) with nested @overload blocks and have no explicit def call definition
  • commands with legitimate call overrides (stdin protocol, input validation, non-trivial option routing) use explicit YARD docs instead and do not carry the # @!method directive
  • commands with call overrides use Base#with_stdin for stdin feeding and delegate exit-status validation to validate_exit_status!
2. Arguments DSL consistency
  • shared options use same alias/modifier patterns
  • shared entries appear in same relative order
  • command-specific differences are intentional and documented
  • no literal entries for policy/output-control flags (--no-edit, --verbose, --no-progress, --no-color, etc.) — command classes are neutral, faithful representations of the git CLI; all siblings use flag_option / value_option for these, leaving policy decisions to the facade. See "Command-layer neutrality" in CONTRIBUTING.md.
Show full SKILL.md (242 more words)Show less
3. Exit-status consistency
  • siblings with same git exit semantics use same allow_exit_status range
  • rationale comments are present and consistent in tone
  • commands without non-zero successful exits do not declare custom ranges
4. YARD consistency
  • consistent class summaries and @api private
  • @overload coverage consistent for equivalent call shapes
  • @return and @raise wording consistent across siblings — @raise [Git::FailedError] uses the canonical generic form ("if git exits with a non-zero exit status" for default range; "if git exits outside the allowed range (exit code > N)" for non-default); never enumerates specific failure causes
  • tag short descriptions do not end with punctuation
  • multi-paragraph tag descriptions have a blank comment line between the short description and each continuation paragraph
5. Unit spec consistency
  • expectations include raise_on_failure: false where command invocation is asserted
  • similar option paths use similar context naming
  • exit-status tests are parallel where ranges are shared
6. Integration spec consistency
  • success/failure grouping uses same structure
  • no output-format assertions (smoke + error handling only)
7. Migration process consistency

See Command Implementation § Phased rollout requirements for the canonical checklist. During a cross-command audit, verify that sibling commands were migrated in the same slice and that the same quality gates were applied.

Output

  1. Summary table:

    AspectFile AFile BFile CStatus

  2. Inconsistency list with canonical recommendation:

    IssueFilesRecommended canonical form

Branch workflow: Implement any fixes on a feature branch. Never commit or push directly to main — open a pull request when changes are ready to merge.

© ruby-git, MIT. 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 .github/skills/review-cross-command-consistency of ruby-git/ruby-git.

Open the folder on GitHubat commit f3bf20f

Compare with similar skills

Review Cross Command Consistency 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.

Review Cross Command Consistency compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Cross Command Consistency this skillruby-git/ruby-git1.8k—~1.6kAutomated safety check: PassMIT
Tabler Class Reference Tablestabler/tabler42k—~1.4kAutomated safety check: PassMIT
Nap Consistencythedaviddias/Front-End-Checklist74k—~613Automated safety check: PassMIT
Consistent Helpthedaviddias/Front-End-Checklist74k—~482Automated safety check: PassMIT
GDD Consistency CheckDonchitos/Claude-Code-Game-Studios26k—~3.5kAutomated safety check: NotesMIT
Large Class Stylesgl-project/sglang37k2 repos~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Tabler Class Reference Tables

    tabler/tabler

    Writes or updates the classnames front matter that renders the class table at the end of a Tabler component docs page.

    42k GitHub stars~1.4k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Nap Consistency

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a local business website for local SEO.

    74k GitHub stars~613 tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Consistent Help

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing support UI across multi-page flows such as checkout, onboarding, account recovery, or support journeys.

    74k GitHub stars~482 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • GDD Consistency Check

    Donchitos/Claude-Code-Game-Studios

    Compares every game design document against the entity registry to find cross-document conflicts such as differing stats, using a grep-first scan that avoids full reads.

    26k GitHub stars~3.5k tokensUpdated 8 days ago
    Game DevelopmentAuto-check: notes

  • Large Class Style

    sgl-project/sglang

    Code style for SGLang large classes Scheduler, TokenizerManager, and ModelRunner: frozen-code conventions and init orchestration style.

    37k GitHub starsUsed in 2 repos~1.9k tokens
    AI & LLM EngineeringAuto-check passed

  • Kl Consistency Test

    sgl-project/sglang

    Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths…

    37k GitHub starsUsed in 2 repos~3.7k tokens
    AI & LLM EngineeringAuto-check passed

More from ruby-git/ruby-git

All 30 skills in this repo

  • Address PR Feedback for ruby-git

    ruby-git/ruby-git

    Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…

    1.8k GitHub stars~657 tokensUpdated 5 days ago
    Auto-check passed

  • Breaking Change Analysis

    ruby-git/ruby-git

    Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.

    1.8k GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed

  • CI/CD Failure Troubleshooting

    ruby-git/ruby-git

    Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

  • Git Command Class Implementation

    ruby-git/ruby-git

    Scaffolds and reviews `Git::Commands::*` classes in the ruby-git library, with unit tests, integration tests and YARD docs, using the Base command architecture.

    1.8k GitHub stars~3k tokensUpdated 5 days ago
    Auto-check passed

  • Gem Dependency Management

    ruby-git/ruby-git

    Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.

    1.8k GitHub stars~806 tokensUpdated 5 days ago
    Auto-check passed

  • Extract Command from Git::Lib

    ruby-git/ruby-git

    Migrates a direct command call in Ruby Git's Git::Lib to a Git::Commands class, as part of a Strangler Fig redesign, with a plan, legacy tests and a pull request.

    1.8k GitHub stars~4.4k tokensUpdated 5 days ago
    Auto-check passed

Questions about Review Cross Command Consistency

What does Review Cross Command Consistency do?

Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture. Review Cross Command Consistency is an agent skill from ruby-git/ruby-git. Compares sibling command classes for consistent structure, documentation, testing, and exit-status conventions under the Base architecture.

When should I use Review Cross Command Consistency?

Review Cross Command Consistency fits situations like: cross-command audits.

How do I install Review Cross Command Consistency in Claude Code?

Run `npx skills add ruby-git/ruby-git --skill review-cross-command-consistency -a claude-code`. Or copy the skill folder (.github/skills/review-cross-command-consistency in ruby-git/ruby-git) into .claude/skills/review-cross-command-consistency in your project. Claude Code loads it when a task matches its description.

How do I install Review Cross Command Consistency in Codex?

Run `npx skills add ruby-git/ruby-git --skill review-cross-command-consistency -a codex`. Or copy the skill folder (.github/skills/review-cross-command-consistency in ruby-git/ruby-git) into .agents/skills/review-cross-command-consistency in your project. Codex loads it when a task matches its description.

Can I use Review Cross Command Consistency 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 ruby-git/ruby-git --skill review-cross-command-consistency -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-cross-command-consistency, .gemini/skills/review-cross-command-consistency, .github/skills/review-cross-command-consistency and .opencode/skills/review-cross-command-consistency in your project.

What does Review Cross Command Consistency need to run?

Going by SKILL.md and its folder, Review Cross Command Consistency needs the command-line tools its instructions call (git).

Does Review Cross Command Consistency 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 Review Cross Command Consistency 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 Review Cross Command Consistency use?

Review Cross Command Consistency 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 Review Cross Command Consistency use?

About 1.6k tokens (SKILL.md is roughly 6.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 Review Cross Command Consistency?

Skills that share tags, products or a category with Review Cross Command Consistency: Tabler Class Reference Tables (tabler/tabler, 42k stars), Nap Consistency (thedaviddias/Front-End-Checklist, 74k stars), Consistent Help (thedaviddias/Front-End-Checklist, 74k stars) and GDD Consistency Check (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Cross Command Consistency?

ruby-git (a GitHub organization) maintains it in ruby-git/ruby-git, which has 1,799 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 2, 2026.

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