srs-develop

Develop, debug, review, and maintain the SRS and Oryx streaming media codebases.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/Ocyss/srs-auth --skill srs-develop-ocyss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: srs-develop
Source: https://github.com/Ocyss/srs-auth/tree/main/.agents/skills/srs-develop
Command: npx skills add https://github.com/Ocyss/srs-auth --skill srs-develop-ocyss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Working on the SRS and Oryx streaming media projects requires navigating multiple repositories, server generations, and verification suites; this Skill routes every development, bug-fix, review, or code-explanation request through a structured workflow grounded in the actual source code and project documentation. ## Core Features & Use Cases - Task Routing: Routes every request to exactly one of six workflows — Develop Code, Scan Issues, Scan PRs, Fix a Bug, Learn Code, or Review a PR — covering the Go proxy, SRS browser player, Dev Docker images, Oryx backend and dashboard, and C++ media server maintenance. - Cross-Component Verification: Enforces a mandatory integration test matrix (proxy E2E, Redis routing, SRT, WHIP, bearer auth) plus bundled Bash and Node.js test scripts for GB28181 session cleanup, Oryx scenarios, and browser player URL generation. - Use Case: A maintainer asks to fix a GB28181 TCP disconnect bug in the C++ server; the Skill routes to Fix a Bug, reproduces the issue with the bundled E2E scripts, implements the minimal fix, runs the full integration suite, and records a Truth Record on the GitHub issue. ## Quick Start Ask the assistant to fix a specific SRS or Oryx issue, implement a planned change to the Go proxy or Oryx backend, review a pull request, or explain how an existing module works.

Frequently Asked Questions about srs-develop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I develop or modify features in the SRS Go proxy?▼

Use the Develop Code workflow, which routes to the proxy server path. It loads the code map and documentation routers, asks you to confirm the target module, then implements the change and runs the full cross-component integration test suite.

How do I fix a reported SRS or Oryx bug?▼

Use the Fix a Bug workflow: verify the issue report against code and documentation, draft a Truth Record for maintainer approval, implement the smallest fix with regression coverage, then publish the verified result back to the GitHub issue.

Can I add new features to the SRS C++ media server?▼

No. The C++ media server is in maintenance mode and only accepts bug fixes, security fixes, compatibility fixes, tests, and documentation corrections. New server features belong in the next-generation Go server, though Go origin and edge workflows are not yet supported.

What tests run after changing SRS runtime code?▼

Every standalone SRS runtime change requires the full integration suite: Go proxy unit tests with coverage, single-origin and multi-origin E2E tests, edge topology, Redis routing, transmux, SRT, WHIP, and bearer-auth scripts, plus any feature-specific bundled tests.

Does this skill handle SRS usage or configuration questions?▼

No. End-user support, usage questions, and configuration help are explicitly out of scope and belong to the separate srs-support skill. This skill covers only development, maintenance, review, and code-explanation tasks.