shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
Best use case
shell-scripts is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
Teams using shell-scripts should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/shell-scripts/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How shell-scripts Compares
| Feature / Agent | shell-scripts | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Shell Scripts Workflow
Workflow for shell script changes.
## Prerequisites
- **Use `git-workflow` Skill** for branch, commit, and PR workflow.
- **Refer to `.claude/rules/shell-script.md`** for detailed best practices (SSOT).
## Applicable Files
| Path | Description |
|------|-------------|
| `scripts/` | All shell scripts |
| `*.sh` | Shell scripts anywhere |
## Workflow
### 1. Make Changes
Edit shell scripts following the rules in `.claude/rules/shell-script.md`.
### 2. Verify (from rules/shell-script.md)
```bash
make shfmt
shellcheck scripts/{script}.sh # if installed
```
### 3. Self-Review Checklist
- [ ] Script is executable (`chmod +x`)
- [ ] Has shebang line (`#!/usr/bin/env bash`)
- [ ] Uses strict mode (`set -euo pipefail`)
- [ ] Variables are quoted
- [ ] All comments and messages are in English
## Related
- `.claude/rules/shell-script.md` - Shell rules (SSOT)
- `git-workflow` - Branch, commit, PR workflowRelated Skills
wallet-cli
How to run watch, keygen, and sign wallet CLI commands. Use when executing wallet commands or testing wallet functionality.
typescript-development
TypeScript/JavaScript development workflow for apps/ directory. Use when modifying TypeScript code in xrpl-grpc-server or JavaScript in eth-contracts.
solidity-development
Solidity smart contract development workflow. Use when modifying smart contracts in apps/eth-contracts/contracts/.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
mockery
Mock generation workflow for go-crypto-wallet. Activate whenever a developer asks to generate a mock for a new interface, add test coverage that requires a mock, or replace a manually-written test stub for a ports interface. Claude MUST use `make mockery` — never write mock struct code by hand.
makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
label-context-mapping
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
knowledge-gap
Post-task knowledge gap review and proposals for improving skills/rules
go-development
Go development workflow including verification commands and self-review checklist. Use when modifying Go code in internal/, pkg/, or cmd/ directories.