Skip to content

Ocyss/srs-auth / .agents/skills/srs-develop

srs-develop

Verified

Develop, modify, debug, review, maintain, and explain the SRS and Oryx codebases and the SRS Docker image toolchain. Use for planned changes to the next-generation SRS Go proxy, SRS browser player, ossrs/dev-docker images, or Oryx Go backend, React dashboard, integrated runtime, packaging, installers, releases, and tests; bug maintenance; issue and pull-request triage; pull-request review; and Learn Code questions. The C++ SRS server is in maintenance mode, and planned Go origin and edge development is not yet supported. NOT for end-user support, usage questions, or configuration help — use srs-support for those.

FileKindSize
SKILL.mdskill md8.2 KB
references/develop-code.mdmarkdown15.1 KB
references/fix-a-bug.mdmarkdown6.6 KB
references/integration-tests.mdmarkdown2.9 KB
references/learn-code.mdmarkdown3.3 KB
references/oryx-issues.mdmarkdown218 B
references/oryx-local-development.mdmarkdown11.9 KB
references/review-a-pr.mdmarkdown3.5 KB
references/scan-issues.mdmarkdown993 B
references/scan-prs.mdmarkdown1.4 KB
references/srs-issues.mdmarkdown58.5 KB
references/version-and-changelog.mdmarkdown2.3 KB
scripts/browser-page-url-test.jsscript2.7 KB
scripts/gb28181-api-timeout-test.shscript5.3 KB
scripts/gb28181-create-session.shscript2.1 KB
scripts/gb28181-publish-stream.shscript3.9 KB
scripts/gb28181-tcp-disconnect-test.shscript4.3 KB
scripts/oryx-api-smoke-test.shscript4.2 KB
scripts/oryx-camera-test.shscript12.2 KB
scripts/oryx-forward-test.shscript10.9 KB
scripts/oryx-live-room-test.shscript10.2 KB
scripts/oryx-live-streaming-test.shscript12.6 KB
scripts/oryx-record-test.shscript10.4 KB
scripts/oryx-run-tests.shscript2.3 KB
scripts/oryx-stack-start.shscript5.2 KB
scripts/oryx-stack-stop.shscript1.8 KB
scripts/oryx-transcode-test.shscript9.8 KB
scripts/oryx-vlive-test.shscript12.0 KB
scripts/proxy-e2e-bearer-auth-test.shscript12.0 KB
scripts/proxy-e2e-cluster-test.shscript10.4 KB
scripts/proxy-e2e-edge-test.shscript10.6 KB
scripts/proxy-e2e-redis-test.shscript11.7 KB
scripts/proxy-e2e-srt-test.shscript9.5 KB
scripts/proxy-e2e-test.shscript5.7 KB
scripts/proxy-e2e-transmux-test.shscript7.3 KB
scripts/proxy-e2e-whip-test.shscript11.5 KB
scripts/proxy-utest.shscript1.5 KB
scripts/setup-ffmpeg-with-whip.shscript7.5 KB

scripts/oryx-run-tests.sh

View on GitHub
#!/bin/bash
# Runs every Oryx local verification script in parallel against one shared
# stack: starts the stack (oryx-stack-start.sh), launches all test scripts
# backgrounded and waits for them, always stops the stack afterward
# (oryx-stack-stop.sh) regardless of pass/fail, then prints a summary.
#
# This exists so "run all the tests" is one command instead of a hand-typed
# background/wait snippet that is easy to paste wrong and end up serialized.
# Add new oryx-*-test.sh scripts to TEST_SCRIPTS below to include them here.

SCRIPT_DIR="$(cd -P "$(dirname "$0")" && pwd)"

TEST_SCRIPTS=(
  oryx-api-smoke-test.sh
  oryx-live-streaming-test.sh
  oryx-live-room-test.sh
  oryx-forward-test.sh
  oryx-record-test.sh
  oryx-transcode-test.sh
  oryx-vlive-test.sh
  oryx-camera-test.sh
)

echo "=== Oryx Test Suite ==="
echo "Scripts: ${TEST_SCRIPTS[*]}"
echo ""

bash "$SCRIPT_DIR/oryx-stack-start.sh"
START_STATUS=$?
if [[ "$START_STATUS" -ne 0 ]]; then
  echo "FAIL: oryx-stack-start.sh failed, aborting before any test runs." >&2
  exit "$START_STATUS"
fi
echo ""

echo "=== Running ${#TEST_SCRIPTS[@]} test scripts in parallel ==="
# Plain indexed arrays only -- the default macOS /bin/bash is 3.2 and has no
# associative arrays (declare -A). LOG_FILES[i] corresponds to
# TEST_SCRIPTS[i] and PIDS[i] by matching index.
LOG_FILES=()
PIDS=()
for name in "${TEST_SCRIPTS[@]}"; do
  log="/tmp/oryx-run-tests-$name.log"
  LOG_FILES+=("$log")
  bash "$SCRIPT_DIR/$name" >"$log" 2>&1 &
  PIDS+=("$!")
  echo "Started $name (pid $!), log: $log"
done
echo ""

FAILED_NAMES=()
FAILED_LOGS=()
for i in "${!TEST_SCRIPTS[@]}"; do
  name="${TEST_SCRIPTS[$i]}"
  pid="${PIDS[$i]}"
  if wait "$pid"; then
    echo "PASS: $name"
  else
    echo "FAIL: $name"
    FAILED_NAMES+=("$name")
    FAILED_LOGS+=("${LOG_FILES[$i]}")
  fi
done
echo ""

# Always tear down the shared stack, whether tests passed or not.
bash "$SCRIPT_DIR/oryx-stack-stop.sh"
echo ""

if [[ "${#FAILED_NAMES[@]}" -gt 0 ]]; then
  echo "=== Failed scripts: ${FAILED_NAMES[*]} ==="
  for i in "${!FAILED_NAMES[@]}"; do
    echo ""
    echo "--- ${FAILED_NAMES[$i]} output (${FAILED_LOGS[$i]}) ---"
    cat "${FAILED_LOGS[$i]}"
  done
  echo ""
  echo "=== Oryx Test Suite FAILED ==="
  exit 1
fi

echo "=== Oryx Test Suite PASSED (${#TEST_SCRIPTS[@]}/${#TEST_SCRIPTS[@]}) ==="
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall