Skip to content

KamiJeong/tech-bridge-book / .agents/skills/speckit-guards

speckit-guards

Verified

Guard scripts for Codex Spec Kit multi-agent workflow safety and token observability.

FileKindSize
SKILL.mdskill md1.7 KB
scripts/generate-token-report.shexecutablescript5.9 KB
scripts/guard-before-commit.shexecutablescript1.0 KB
scripts/guard-before-implement.shexecutablescript1.3 KB
scripts/guard-before-pr.shexecutablescript1007 B
scripts/guard-no-app-code-change.shexecutablescript737 B
scripts/guard-token-analyzer-available.shexecutablescript1.4 KB
scripts/record-token-step.shexecutablescript4.4 KB
scripts/validate-agent-definitions.shexecutablescript3.7 KB

scripts/guard-no-app-code-change.sh

View on GitHub
#!/usr/bin/env bash
set -euo pipefail

BASE_REF="${1:-HEAD}"
allowed_regex='^(\.codex/|\.agents/|\.specify/token-analysis/|specs/|AGENTS\.md$|\.gitignore$)'

if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
  echo "PASS: not a git repository; no app-code diff check available"
  exit 0
fi

mapfile -t changed < <(git diff --name-only "$BASE_REF" --)
violations=()
for path in "${changed[@]}"; do
  if [[ ! "$path" =~ $allowed_regex ]]; then
    violations+=("$path")
  fi
done

if [[ "${#violations[@]}" -gt 0 ]]; then
  echo "FAIL: changes outside allowed workflow artifact paths:" >&2
  printf '  %s\n' "${violations[@]}" >&2
  exit 1
fi

echo "PASS: no application code changes detected outside workflow artifact paths"
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall