mirror of
https://github.com/obra/superpowers
synced 2026-07-16 07:34:30 +00:00
Gaurav Dubey
2b1c06a849
Commit e7ddc25 ('Prune per-harness tool-mapping boilerplate') deliberately
removed the skill-loading explainers and generic action->tool tables from
antigravity-tools.md and pi-tools.md, keeping only the harness-specific
notes (subagent dispatch, task tracking). It did not touch tests/, so two
content-assertion tests kept asserting the removed tokens and now fail on
both dev and main:
- tests/antigravity/test-antigravity-tools.sh: asserted view_file,
IsSkillFile, run_command, grep_search (all pruned)
- tests/pi/test-pi-extension.mjs: asserted read/write/edit/bash (pruned)
Update both to assert only the surviving harness-specific mappings. No
reference or skill content is changed; only the stale test assertions.
47 lines
2.1 KiB
Bash
Executable File
47 lines
2.1 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Validate the Antigravity (agy) integration. agy installs the existing plugin
|
|
# directly (`agy plugin install <repo-url>`): it loads the bundled skills and
|
|
# runs the SessionStart hook for bootstrap, so there is no agy-specific scaffold
|
|
# to test. What IS agy-specific is the tool mapping — subagent dispatch via
|
|
# invoke_subagent (self/research types) and task tracking via a task artifact —
|
|
# and SKILL.md pointing at it.
|
|
#
|
|
# Mirrors tests/pi/test-pi-extension.mjs's "tools reference documents
|
|
# harness-specific mappings" check. CI-safe: does not require `agy` installed.
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
|
|
|
|
MAPPING="$REPO_ROOT/skills/using-superpowers/references/antigravity-tools.md"
|
|
SKILL="$REPO_ROOT/skills/using-superpowers/SKILL.md"
|
|
|
|
fail() { echo "FAIL: $*" >&2; exit 1; }
|
|
|
|
echo "test-antigravity-tools: checking Antigravity tool mapping"
|
|
|
|
# --- Mapping exists ---------------------------------------------------------
|
|
[ -f "$MAPPING" ] || fail "tool mapping missing at $MAPPING"
|
|
|
|
# --- Core action→tool mappings are documented -------------------------------
|
|
for tool in write_to_file replace_file_content invoke_subagent; do
|
|
grep -q "$tool" "$MAPPING" \
|
|
|| fail "mapping does not document the '$tool' tool"
|
|
done
|
|
|
|
# --- Subagents use the built-in self/research types -------------------------
|
|
grep -q '`self`' "$MAPPING" \
|
|
|| fail "mapping does not document the built-in 'self' subagent type"
|
|
grep -q '`research`' "$MAPPING" \
|
|
|| fail "mapping does not document the built-in 'research' subagent type"
|
|
|
|
# --- Task tracking documents the 'task' artifact mechanism ------------------
|
|
grep -qE 'ArtifactType.*task|task. artifact' "$MAPPING" \
|
|
|| fail "mapping does not document task tracking as a 'task' artifact"
|
|
|
|
# --- SKILL.md Platform Adaptation links the mapping -------------------------
|
|
grep -q "antigravity-tools.md" "$SKILL" \
|
|
|| fail "SKILL.md Platform Adaptation does not reference antigravity-tools.md"
|
|
|
|
echo "PASS: Antigravity tool mapping valid (subagent dispatch, task artifact, SKILL.md link)"
|