aqwa-batch-execution-debug-sequence
Sub-skill of aqwa-batch-execution: Debug Sequence.
Best use case
aqwa-batch-execution-debug-sequence is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of aqwa-batch-execution: Debug Sequence.
Teams using aqwa-batch-execution-debug-sequence 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/debug-sequence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How aqwa-batch-execution-debug-sequence Compares
| Feature / Agent | aqwa-batch-execution-debug-sequence | 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 aqwa-batch-execution: Debug Sequence.
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
# Debug Sequence
## Debug Sequence
```bash
# Step 1 — check license
echo "License: $ANSYSLMD_LICENSE_FILE"
lmstat -a -c $ANSYSLMD_LICENSE_FILE 2>/dev/null | grep -i aqwa
# Step 2 — run with all output captured
${AQWA_EXE} std analysis 2>&1 | tee analysis.run.log
# Step 3 — triage .MES (most informative)
cat analysis.mes
# Step 4 — scan .LIS for fatal lines
grep -n "FATAL\|ERROR\|STOP\|WARNING" analysis.lis | head -40
# Step 5 — confirm panel count echo
grep "TOTAL NUMBER OF PANELS" analysis.lis
```Related Skills
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
toml-section-scoping-debug
Identify and fix TOML configuration errors caused by misplaced keys inside section headers
toml-section-scoping-config-debug
Diagnose TOML config errors caused by misplaced keys in table sections
test-driven-hook-debugging
Debugging and fixing shell hooks by writing isolated test suites first, then using test failures to pinpoint logic bugs
tax-software-duplicate-adjustment-debugging
Identify and fix duplicate tax adjustments entered through multiple mechanisms in tax software
python-import-path-mismatch-debugging
Diagnose and fix ModuleNotFoundError when a package is installed but imports still fail due to environment/path mismatches
python-import-path-debugging
Diagnose ModuleNotFoundError when a package is installed but still fails to import
multi-layer-stale-state-debugging
Detect and clear stale state persisting across multiple storage layers (auth files, cache, code logic)
debug-toml-section-scoping-errors
Diagnose and fix TOML configuration errors caused by misplaced key-value pairs in named sections