srs-develop

name

srs-develop

description

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.

SRS and Oryx Development

Core Principle

Code and documents are the only truth. Issue descriptions may be inaccurate. Pull requests may be misleading. Feature descriptions may be insufficient. Always ground your understanding in the actual source code and project documentation. Documents capture design intent, architecture rationale, and complex background that code alone cannot express — they are another form of code. When code and documents conflict, investigate rather than assume one is wrong.

Skill Dependencies

• skills/internal-docs-for-srs/SKILL.md — Route and load project documentation. This skill remains responsible for the development workflow and final result.
• skills/internal-codemap-for-srs/SKILL.md — Route code navigation and verification to the relevant server map. This skill remains responsible for the development workflow and final result.

Cross-Component Verification

For every standalone SRS runtime code change in either the Go proxy or C++ media server, run the complete bundled suite in references/integration-tests.md in addition to module-specific unit, black-box, protocol E2E, sanitizer, or benchmark verification. Apply this requirement during development, bug fixing, and pull-request review; do not treat the proxy-* script names as limiting the suite to proxy changes.

Version and Changelog