Skip to content

donaldfilimon/abi / .agents/skills/backend-diagnostics

backend-diagnostics

Verified

Build the abi CLI and report GPU / accelerator / shader / MLIR backend status and the compute-backend matrix (CPU/GPU/NPU/TPU detection + dynamic selection). Use when asked about backend capabilities, why a backend shows accelerated=false, or to capture a hardware/dispatch report.

FileKindSize
SKILL.mdskill md1.5 KB
diag.shexecutablescript1.3 KB
#!/usr/bin/env bash
# backend-diagnostics driver: build the abi CLI and capture the GPU / accelerator
# / shader / MLIR backend report plus the compute-backend matrix. Asserts the
# stable section markers. Resolves the repo root from its own location.
#
# Usage: .agents/skills/backend-diagnostics/diag.sh
set -uo pipefail
SCRIPT_DIR=$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)
REPO_ROOT=$(cd -- "$SCRIPT_DIR/../../.." && pwd)
cd "$REPO_ROOT"
ABI="$REPO_ROOT/target/debug/abi"
fail=0
say() { printf '\n=== %s ===\n' "$*"; }
check() { local label="$1" expect="$2"; shift 2; local out; out=$("$@" 2>&1)
    printf '%s\n' "$out"
    grep -qF -- "$expect" <<<"$out" && echo "[ok] $label" || { echo "[FAIL] $label (missing: $expect)"; fail=$((fail+1)); }; }

say "build cli"
./tools/cargo.sh build -p abi-cli >/dev/null 2>&1 && echo "[ok] build" || { echo "[FAIL] build"; exit 1; }
[ -x "$ABI" ] || { echo "[FAIL] no binary"; exit 1; }

check "backends report"  "Compute Backends:"    "$ABI" backends
check "compute matrix"   "compute backends"    "$ABI" wdbx compute info
check "gpu info"         "gpu backend="         "$ABI" wdbx gpu info

say "summary"; echo "failed: $fail"
[ "$fail" -eq 0 ] && echo "RESULT: PASS — backend diagnostics captured." || echo "RESULT: FAIL — $fail check(s)."
exit "$fail"
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall