parallel-batch-executor-1-always-set-a-default
Sub-skill of parallel-batch-executor: 1. Always Set a Default (+4).
Best use case
parallel-batch-executor-1-always-set-a-default is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of parallel-batch-executor: 1. Always Set a Default (+4).
Teams using parallel-batch-executor-1-always-set-a-default 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/1-always-set-a-default/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How parallel-batch-executor-1-always-set-a-default Compares
| Feature / Agent | parallel-batch-executor-1-always-set-a-default | 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?
Sub-skill of parallel-batch-executor: 1. Always Set a Default (+4).
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
# 1. Always Set a Default (+4)
## 1. Always Set a Default
```bash
PARALLEL="${PARALLEL:-5}"
```
## 2. Validate Input
```bash
[[ $PARALLEL -gt 0 ]] || die "Parallelism must be positive"
[[ $PARALLEL -le 50 ]] || log_warning "High parallelism may overwhelm system"
```
## 3. Handle Failures Gracefully
```bash
# Don't use set -e with xargs - it will mask failures
# Instead, track failures explicitly
```
## 4. Log Everything
```bash
# Create per-task logs for debugging
log_file="$LOG_DIR/task_$(date +%s)_$$.log"
```
## 5. Clean Up Resources
```bash
trap cleanup EXIT INT TERM
```Related Skills
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
parallel-array-alignment-pattern
Maintain index synchronization between parallel arrays when adding new entries to preserve label-path mappings
batch-syntax-repair-from-injection-errors
Detect and fix systematic syntax errors caused by line-injection scripts that split multiline constructs
batch-syntax-fix-with-regex-line-based-fallback
Fix repeated syntax errors across many files using regex, then fall back to line-based parsing when regex fails
batch-syntax-fix-regex-iteration
Iteratively fix widespread syntax errors across many files using regex refinement when initial patterns fail
batch-syntax-fix-pattern
Identify and repair cascading import/syntax errors across multiple files using regex-based line-scanning and verification
batch-regex-fix-import-syntax
Detect and fix mid-import blank-line syntax breaks across multiple files using line-based regex
parallel-llm-wiki-gap-to-issues
Use parallel subagents to mine remaining LLM-wiki/document-intelligence gaps, de-duplicate against existing GitHub issues, then create only the strongest bounded follow-on issues.
large-parallel-planning-wave-environment-failure-handoff
Handle large pre-plan-review planning waves that succeed analytically but fail to persist artifacts due to quota exhaustion, sandbox write failures, or cancelled GitHub mutations.
closure-first-overnight-batch
Run a high-leverage overnight batch by clearing stale-open approved issues first, converting shared blockers into tracked issues, and reserving only one lane for true implementation.
workspace-hub-batch-issue-execution
Deprecated alias for gh-work-execution.
parallel-approved-issue-worktrees
Launch approved GitHub issue implementation in parallel using isolated git worktrees, committed execution-pack prompts, local plan-approved markers, and direct background Codex runs when delegate_task workers are unreliable for real repo writes.