mcpbeat

ROSA Command Authoring

openshift/rosa command authoring

Add or edit Cobra commands in openshift/rosa while keeping command wiring thin and package logic aligned with repo structure.

387 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
103
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/openshift/rosa --skill ROSA Command Authoring

The instruction itself

3 sections, as written by the author

ROSA Command Authoring

Use this skill when:

  • Adding a new rosa command or subcommand
  • Changing flags or command help
  • Moving logic between cmd/ and pkg/
  • Refactoring command execution flow

Workflow

  • Read AGENTS.md and guidelines/command-guidelines.md, then inspect the nearest similar command implementation.
  • Keep Cobra command files thin and move non-Cobra logic into pkg/.
  • Follow the entrypoint and exit pattern already established in the nearest similar command area.
  • Many ROSA commands use Run: run; do not switch a command area between Run and RunE, or add/remove direct os.Exit() calls, unless the surrounding pattern already does so and the change keeps behavior consistent.
  • Reuse output, reporter, and interactive patterns already used by the surrounding command area.
  • If the command tree changes, update cmd/rosa/structure_test/command_structure.yml.
  • If supported flags change, update the matching cmd/rosa/structure_test/command_args/**/command_args.yml.
  • When command help or docs change, check whether make generate-docs is part of the required verification.

Verification

  • make fmt
  • relevant package tests or make test
  • make rosa
  • make generate-docs when command docs or help output changed

Follow CONTRIBUTING.md for the exact contributor workflow and hook expectations.

How to use it

Copy the folder

Take openshift/rosa command authoring from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.