Reviewing CLI Command Agent Skill

Provides checklist for reviewing Typer CLI command implementations. Covers structure, Annotated syntax, error handling, exit codes, display module usage, destructive action patterns, and help text conventions. Use when user asks to review/check/verify a CLI command, wants feedback on implementation, or asks if a command follows best practices.

857 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1335

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/https-deeplearning-ai/sc-agent-skills-files --skill reviewing-cli-command

The instruction itself

10 sections, as written by the author

Reviewing CLI Commands

Checklist for reviewing Typer CLI command implementations.

Review Process

Read the command file
Check each section below
Report findings using output format at bottom

Structure

[ ] File in src/<cli_app>/commands/
[ ] Has app = typer.Typer() and @app.command()
[ ] Command groups use @app.command() for each subcommand
[ ] Registered in commands/__init__.py with add_typer()
[ ] Single commands: add_typer(app) without name
[ ] Command groups: add_typer(app, name="group")

Arguments & Options

[ ] Uses Annotated syntax
[ ] Arguments for required positional input
[ ] Options for optional named parameters
[ ] Short flags where appropriate (-f, -q)
[ ] Help text: lowercase, no period, brief

# GOOD:
name: Annotated[str, typer.Argument(help="item name")]
force: Annotated[bool, typer.Option("--force", "-f", help="skip confirmation")] = False

# BAD:
name: str = typer.Argument(..., help="The name of the item.")

Error Handling

[ ] Validates input before processing
[ ] Exit codes: 0=success, 1=error, 2=invalid input
[ ] Errors via display.error()
[ ] Uses raise typer.Exit(code) after errors
[ ] Uses raise typer.Abort() for cancellation

# GOOD:
if id < 1:
    display.error("ID must be positive")
    raise typer.Exit(EXIT_INVALID_INPUT)

# BAD:
if id < 1:
    print("Error: ID must be positive")
    return

Output

[ ] All output through display module
[ ] No print(), typer.echo(), or console.print()

# GOOD:
display.success(f"Added '{task.title}'")

# BAD:
print(f"Added '{task.title}'")

Destructive Actions

[ ] Has --force / -f flag
[ ] typer.confirm() with default=False
[ ] Shows "Cancelled" on abort

# GOOD:
if not force:
    confirm = typer.confirm(f"Delete '{task.title}'?", default=False)
    if not confirm:
        display.info("Cancelled")
        raise typer.Abort()

# BAD: defaults to Yes
confirm = typer.confirm(f"Delete?", default=True)

Help Text

[ ] Docstring exists
[ ] Imperative mood ("Add a task" not "Adds a task")
[ ] First line < 60 characters

Common Mistakes

| Mistake | Fix |

|---------|-----|

| print() | display.success/error/warning/info() |

| Wrong exit code | 0=success, 1=error, 2=invalid |

| Missing --force on delete | Add force option with default False |

| Confirmation defaults Yes | default=False in typer.confirm() |

| Old Typer syntax | Annotated[type, typer.Argument()] |

| Missing app = typer.Typer() | Each command file needs its own app |

| Not registered | add_typer(app) in commands/__init__.py |

Review Output Format

## Review: <command_name>

[OK] Uses Annotated syntax
[OK] Has docstring in imperative mood
[X] Missing --force flag on destructive command
[X] Uses print() instead of display module
[!] Help text could be shorter

### Summary
<brief summary of issues found>

### Suggested Fixes
<code suggestions if needed>

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take https-deeplearning-ai/reviewing-cli-command 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.