cuozg/bash-check
skills/bash-check/SKILL.md
Use this skill to validate a shell script before committing or deploying — runs bash -n syntax checks and ShellCheck static analysis, then produces a findings report. Use it whenever the user has a .sh or .bash script they want checked for bugs, unsafe patterns, or POSIX compliance, even if they just say "is this script OK" or "check this for issues." Do not use for refactoring or optimizing scripts — use bash-optimize for that.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills bash-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 12:52 PM210.2s2 files scanned
SKILL.md
- name:
- bash-check
- description:
- >
- author:
- kuozg
- version:
- 1.0
bash-check
Validate shell scripts using bash -n syntax checking and ShellCheck static analysis, then produce a findings report.
When to Use
- Before committing or deploying a shell script
- Auditing an existing script for latent bugs or unsafe patterns
- Verifying a script written by another author
- CI pre-check for shell scripts in a repository
Workflow
- Read — Read the target script in full
- Syntax — Run
bash -n {script}to catch parse errors - Lint — Run
shellcheck {script}to get all warnings and errors - Review — Manually check: quoting,
set -e/-u/-o pipefail, uninitialized variables, subshell leaks - Report — Compile findings into a validation report with severity, line, description, and suggested fix
Rules
- Run both
bash -nandshellcheck— neither alone is sufficient - Report every finding, not just errors — warnings matter
- Include the fix for each finding, not just the problem
- Note any
# shellcheck disablesuppressions and whether they are justified
Output Format
Validation report listing: severity (error/warning/info), line number, ShellCheck code, description, and suggested fix. Summary line: pass/fail with finding count.
Reference Files
references/shellcheck-rules.md— common ShellCheck codes and their fixes
Load references on demand via read_skill_file("bash-check", "references/{file}").
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026