reviewing-cli-command
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
Install / Use
npx skills add https-deeplearning-ai/sc-agent-skills-files --skill reviewing-cli-commandInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of reviewing-cli-command
reviewing-cli-command scores 84/100 on our quality scale, 2902nd of 4,698 Development & Engineering skills we index.
Its SKILL.md is 3.3 KB long, well organised into 21 sections with 5 code examples: a solid amount of guidance for an agent.
With 1,391 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 5 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-11-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 86/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
reviewing-cli-command compared with similar skills
All 4 of these similar skills score higher than reviewing-cli-command; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| reviewing-cli-command (this skill)by https-deeplearning-ai | 84 | 1.4k | 5mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install reviewing-cli-command?
- Run
npx skills add https-deeplearning-ai/sc-agent-skills-files --skill reviewing-cli-command. The install tabs above show the steps for each supported agent. - Which AI agents does reviewing-cli-command work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is reviewing-cli-command safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 86/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is reviewing-cli-command still maintained?
- The repository was last updated about 5 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: reviewing-cli-command description: 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.
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__.pywithadd_typer() - [ ] Single commands:
add_typer(app)without name - [ ] Command groups:
add_typer(app, name="group")
Arguments & Options
- [ ] Uses
Annotatedsyntax - [ ] 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
displaymodule - [ ] No
print(),typer.echo(), orconsole.print()
# GOOD:
display.success(f"Added '{task.title}'")
# BAD:
print(f"Added '{task.title}'")
Destructive Actions
- [ ] Has
--force/-fflag - [ ]
typer.confirm()withdefault=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>
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
