Bash Scripting Workflow workflow skill. Use this skill when the user needs Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Bash Scripting Workflow workflow skill. Use this skill when the user needs Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/bash-scripting from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Bash Scripting Workflow
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Script Template, Quality Gates, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
Creating automation scripts
Writing system administration tools
Building deployment scripts
Developing backup solutions
Creating CI/CD scripts
Use when the request clearly matches the imported source intent: Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
bash-pro - Professional scripting
bash-defensive-patterns - Defensive patterns
Define script purpose
Identify inputs/outputs
Plan error handling
Design logging strategy
Document requirements
Imported Workflow Notes
Imported: Workflow Phases
Phase 1: Script Design
Skills to Invoke
bash-pro - Professional scripting
bash-defensive-patterns - Defensive patterns
Actions
Define script purpose
Identify inputs/outputs
Plan error handling
Design logging strategy
Document requirements
Copy-Paste Prompts
Use @bash-pro to design production-ready bash script
Phase 2: Script Structure
Skills to Invoke
bash-pro - Script structure
bash-defensive-patterns - Safety patterns
Actions
Add shebang and strict mode
Create usage function
Implement argument parsing
Set up logging
Add cleanup handlers
Copy-Paste Prompts
Use @bash-defensive-patterns to implement strict mode and error handling
Phase 3: Core Implementation
Skills to Invoke
bash-linux - Linux commands
linux-shell-scripting - Shell scripting
Actions
Implement main functions
Add input validation
Create helper functions
Handle edge cases
Add progress indicators
Copy-Paste Prompts
Use @bash-linux to implement system commands
Phase 4: Error Handling
Skills to Invoke
bash-defensive-patterns - Error handling
error-handling-patterns - Error patterns
Actions
Add trap handlers
Implement retry logic
Create error messages
Set up exit codes
Add rollback capability
Copy-Paste Prompts
Use @bash-defensive-patterns to add comprehensive error handling
Phase 5: Logging
Skills to Invoke
bash-pro - Logging patterns
Actions
Create logging function
Add log levels
Implement timestamps
Configure log rotation
Add debug mode
Copy-Paste Prompts
Use @bash-pro to implement structured logging
Phase 6: Testing
Skills to Invoke
bats-testing-patterns - Bats testing
shellcheck-configuration - ShellCheck
Actions
Write Bats tests
Run ShellCheck
Test edge cases
Verify error handling
Test with different inputs
Copy-Paste Prompts
Use @bats-testing-patterns to write script tests
Use @shellcheck-configuration to lint bash script
Phase 7: Documentation
Skills to Invoke
documentation-templates - Documentation
Actions
Add script header
Document functions
Create usage examples
List dependencies
Add troubleshooting section
Copy-Paste Prompts
Use @documentation-templates to document bash script
Imported: Related Workflow Bundles
os-scripting - OS scripting
linux-troubleshooting - Linux troubleshooting
cloud-devops - DevOps automation
Imported: Overview
Specialized workflow for creating robust, production-ready bash scripts with defensive programming patterns, comprehensive error handling, and automated testing.
Use @bash-scripting to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @bash-scripting against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @bash-scripting for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @bash-scripting using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/bash-scripting, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Quality Gates
ShellCheck passes
Bats tests pass
Error handling works
Logging functional
Documentation complete
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
