How do I install the Shell Review skill?

Run npx skillmds add majiayu000/shell-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shell Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shell Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shell Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shell Review?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shell Review by majiayu000 — Agent Skill

Name: Shell Review
Rating: 4.2 (5 reviews)
Author: majiayu000

Shell Review

Audit shell scripts for correctness, portability, and common pitfalls. Triggers: shell script, bash, sh, script review, pipeline, exit code Use when: reviewing shell scripts, CI scripts, hook scripts, wrapper scripts DO NOT use when: creating new scripts - use attune:workflow-setup

majiayu000 0cc02ee 2 files · 3.1 KB Updated Sep 9, 2026 567 repo stars

File contents

Shell Script Review

Audit shell scripts for correctness, safety, and portability.

Quick Start

/shell-review path/to/script.sh

When to Use

CI/CD pipeline scripts
Git hook scripts
Wrapper scripts (run-*.sh)
Build automation scripts
Pre-commit hook implementations

Required TodoWrite Items

shell-review:context-mapped
shell-review:exit-codes-checked
shell-review:portability-checked
shell-review:safety-patterns-verified
shell-review:evidence-logged

Workflow

Step 1: Map Context (`shell-review:context-mapped`)

Identify shell scripts:

# Find shell scripts
find . -name "*.sh" -type f | head -20
# Check shebangs
grep -l "^#!/" scripts/ hooks/ 2>/dev/null | head -10

Document:

Script purpose and trigger context
Integration points (make, pre-commit, CI)
Expected inputs and outputs

Step 2: Exit Code Audit (`shell-review:exit-codes-checked`)

@include modules/exit-codes.md

Step 3: Portability Check (`shell-review:portability-checked`)

@include modules/portability.md

Step 4: Safety Patterns (`shell-review:safety-patterns-verified`)

@include modules/safety-patterns.md

Step 5: Evidence Log (`shell-review:evidence-logged`)

Use imbue:evidence-logging to record findings with file:line references.

Summarize:

Critical issues (failures masked, security risks)
Major issues (portability, maintainability)
Minor issues (style, documentation)

Output Format

## Summary
Shell script review findings

## Scripts Reviewed
- [list with line counts]

## Exit Code Issues
### [E1] Pipeline masks failure
- Location: script.sh:42
- Pattern: `cmd | grep` loses exit code
- Fix: Use pipefail or capture separately

## Portability Issues
[cross-platform concerns]

## Safety Issues
[unquoted variables, missing set flags]

## Recommendation
Approve / Approve with actions / Block

Exit Criteria

Exit code propagation verified
Portability issues documented
Safety patterns checked
Evidence logged

---name: shell-reviewdescription: Audit shell scripts for correctness, portability, and common pitfalls. Triggers: shell script, bash, sh, script review, pipeline, exit code Use when: reviewing shell scripts, CI scripts, hook scripts, wrapper scripts DO NOT use when: creating new scripts - use attune:workflow-setup--- # Shell Script Review Audit shell scripts for correctness, safety, and portability. ## Quick Start ```bash /shell-review path/to/script.sh ``` ## When to Use - CI/CD pipeline scripts - Git hook scripts - Wrapper scripts (run-*.sh) - Build automation scripts - Pre-commit hook implementations ## Required TodoWrite Items 1. `shell-review:context-mapped` 2. `shell-review:exit-codes-checked` 3. `shell-review:portability-checked` 4. `shell-review:safety-patterns-verified` 5. `shell-review:evidence-logged` ## Workflow ### Step 1: Map Context (`shell-review:context-mapped`) Identify shell scripts: ```bash # Find shell scripts find . -name "*.sh" -type f | head -20 # Check shebangs grep -l "^#!/" scripts/ hooks/ 2>/dev/null | head -10 ``` Document: - Script purpose and trigger context - Integration points (make, pre-commit, CI) - Expected inputs and outputs ### Step 2: Exit Code Audit (`shell-review:exit-codes-checked`) @include modules/exit-codes.md ### Step 3: Portability Check (`shell-review:portability-checked`) @include modules/portability.md ### Step 4: Safety Patterns (`shell-review:safety-patterns-verified`) @include modules/safety-patterns.md ### Step 5: Evidence Log (`shell-review:evidence-logged`) Use `imbue:evidence-logging` to record findings with file:line references. Summarize: - Critical issues (failures masked, security risks) - Major issues (portability, maintainability) - Minor issues (style, documentation) ## Output Format ```markdown ## Summary Shell script review findings ## Scripts Reviewed - [list with line counts] ## Exit Code Issues ### [E1] Pipeline masks failure - Location: script.sh:42 - Pattern: `cmd | grep` loses exit code - Fix: Use pipefail or capture separately ## Portability Issues [cross-platform concerns] ## Safety Issues [unquoted variables, missing set flags] ## Recommendation Approve / Approve with actions / Block ``` ## Exit Criteria - Exit code propagation verified - Portability issues documented - Safety patterns checked - Evidence logged

Frequently asked questions