Skip to content

feat: add verification script for bounty #61 - CI failure triage skill #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gordonzhaomwrf-a11y wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add verification script for bounty #61 - CI failure triage skill #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions verify/61-check-ci-failure-skill.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
#!/usr/bin/env bash
# Usage: ./verify/61-check-ci-failure-skill.sh <skill-dir>
# Verifies the machine floor for bounty 61: CI failure triage and classification skill.
set -euo pipefail

DIR="${1:?usage: $0 <skill-dir>}"
fail() { echo "FAIL: $1" >&2; exit 1; }

[ -d "$DIR" ] || fail "skill dir not found: $DIR"
[ -f "$DIR/SKILL.md" ] || fail "missing SKILL.md"
[ -f "$DIR/X.yaml" ] || fail "missing X.yaml"

# Check SKILL.md mentions CI failure triage/classification
grep -qiE "ci[ -]?fail|triage|classif" "$DIR/SKILL.md" || fail "SKILL.md does not reference CI failure triage or classification"

# Check X.yaml has required blocks
grep -q "catalog:" "$DIR/X.yaml" || fail "X.yaml missing catalog block"
grep -q "harness:" "$DIR/X.yaml" || fail "X.yaml missing harness block"

# Check for a classification mapping or script (optional, but recommended)
if [ -f "$DIR/classify.yaml" ] || [ -f "$DIR/classify.py" ] || [ -f "$DIR/classify.sh" ]; then
echo " classification artifact found"
fi

# Ensure no unsafe network patterns (SSRF etc.) – if the skill calls external APIs, it must use runx governed tools
if grep -qrE "curl|wget|requests|fetch" "$DIR" 2>/dev/null; then
# If it does network calls, require runx tool manifest
grep -q "runx.tool.manifest.v1" "$DIR/X.yaml" 2>/dev/null || echo "WARNING: network calls detected but no governed tool reference found; REVIEW: must use runx governed tools"
fi

echo "PASS: CI failure triage skill package structure is valid"