Git Command Class Implementation

Workflow

This skill supports three modes. Determine which mode applies before starting:

• Scaffold — creating a new command class from scratch. Follow all steps.
• Update — adding options to an existing command class: skip steps 2, 3a, 3b, and 3c (the class and test files already exist). Start from step 1, then proceed directly to 3d → 3e → 3f → 4 → 5.
• Review — auditing an existing command class for correctness (no changes). Follow all steps but produce findings instead of code.

1. Gather input — collect the target class name and git subcommand from the Input, then fetch the latest-version and minimum-version git documentation per Git documentation for the git command.

2. Determine class structure (scaffold mode only) — decide between a single class and a sub-command namespace per Single class vs. sub-command namespace.

3. For each command / sub-command class, repeat steps 3a–3f:

   a. Scaffold the command class (subagent) (scaffold mode only) — delegate to a subagent: load REFERENCE.md and the YARD Documentation skill, then generate lib/git/commands/{command}.rb using the Command template. Populate the arguments do block with all options from the latest-version docs per Options completeness, applying the Execution-model conflicts, end_of_options placement, and Exit status guidance rules. Pass the fetched git documentation to the subagent.

   Steps 3b and 3c may run in parallel (they produce independent files).

   b. Scaffold unit tests (subagent) (scaffold mode only) — delegate to a subagent: load Command Test Conventions (which loads RSpec Unit Testing Standards), then generate spec/unit/git/commands/{command}_spec.rb following the unit test conventions. Fix all findings, then repeat the review until clean.

   c. Scaffold integration tests (subagent) (scaffold mode only) — delegate to a subagent: load Command Test Conventions, then generate spec/integration/git/commands/{command}_spec.rb following the integration test conventions. Fix all findings, then repeat the review until clean.

   d. Review Arguments DSL (subagent) — delegate to a subagent: load and apply Review Arguments DSL (and its CHECKLIST.md) against the arguments do block. Fix all findings, then repeat the review until clean. Complete this step before starting steps 3e–3f — DSL corrections change the CLI arguments that tests and YARD docs must reflect.

   Steps 3e and 3f may run in parallel (they review independent file sets).

   e. Review Command Tests (subagent) — delegate to a subagent: load and apply Command Test Conventions against the unit and integration spec files. Fix all findings, then repeat the review until clean.

   f. Review YARD Documentation (subagent) — delegate to a subagent: load and apply Command YARD Documentation against the command class. Fix all findings, then repeat the review until clean.

4. Review class shape and declarations — load REFERENCE.md and verify against the Architecture contract, #call override guidance, Exit status guidance, requires_git_version convention, Internal compatibility contract, and Common failures. Additionally:

   • For scaffold and update modes: write or update the Git::Repository::* facade method per Facade delegation and policy options.
   • For migration PRs: verify Phased rollout requirements.

5. Run quality gates — discover the prerequisite tasks for default and run them sequentially, fixing failures before advancing:

   bundle exec ruby -e "require 'rake'; load 'Rakefile'; puts Rake::Task['default'].prerequisites"

   Run each listed task individually in order via bundle exec rake <task> (one task per invocation — never combine multiple tasks in a single command). On failure, fix the issue and re-run that same task. Once it passes, continue to the next task. After all tasks pass, if any task required a fix during this cycle, start a new cycle from the first task using the same one-at-a-time approach. Keep cycling until every task passes on its first attempt with no fixes needed.

Output

For scaffold and update modes, produce:

1. Command class — lib/git/commands/{command}.rb (and optionally the namespace module file for the first command in a namespace)
2. Unit tests — spec/unit/git/commands/{command}_spec.rb
3. Integration tests — spec/integration/git/commands/{command}_spec.rb
4. Facade delegation — updated Git::Repository::* facade method in lib/git/repository/<topic>.rb
5. All quality gates pass — RSpec, RuboCop, YARD, and build all green

For review mode, produce:

Then list required fixes and indicate whether the migration slice is safe to merge under phased-rollout rules.