internal-codemap-for-srs

Routes SRS and Oryx code tasks to focused codebase maps and verification guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Navigating the large SRS and Oryx codebases is error-prone: broad searches across trunk/src/, cmd/, or oryx/platform/ waste time and surface irrelevant files. This Skill routes each code task to the smallest trusted module map so reading, modifying, and verifying code stays scoped and accurate. ## Core Features & Use Cases - Reference Router: Classifies tasks into six code areas (C++ media server, Go proxy server, browser clients, Docker build images, testing, Oryx) and loads only the matching reference map. - Trusted Navigation Scope: Each reference lists exact modules and files, forbidding broad greps of repository roots and preventing ad-hoc route discovery. - Verification Guidance: Maps unit, black-box, E2E, integration, and benchmark tests to the correct binaries and commands for each codebase. - Use Case: When asked to fix an HLS playback bug in the C++ server, the Skill routes to references/cpp-server.md, identifies app_hls and app_fragment as the responsible modules, and points to the HLS black-box test for verification. ## Quick Start Ask the assistant to locate and fix a bug in the SRS WebRTC publish path, and it will route through the code map to the responsible modules and tests.

Frequently Asked Questions about internal-codemap-for-srs

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

FAQPage Schema
How do I find the right SRS source file for a bug fix?▼

Classify the task by code area first, then load the matching reference map such as references/cpp-server.md for the C++ server. The map lists modules with their responsibilities, so you read only the smallest relevant file set instead of searching trunk/src/ broadly.

What is the difference between the SRS C++ server and the Go server?▼

The C++ server under trunk/src/ is the full-featured origin and edge media server using State Threads coroutines. The Go server under cmd/ and internal/ is the next-generation implementation that currently provides only a stateless proxy in front of C++ origins.

Does this code map cover the Oryx platform?▼

Yes, references/oryx.md covers the Oryx Go backend, React dashboard, runtime packaging, installers, release service, and integration tests. It requires the Oryx checkout to be available at the project-root-relative oryx/ path.

Which SRS tests should I run after a code change?▼

The testing reference maps verification by type: unit tests in trunk/src/utest/, black-box tests and E2E protocol tests in trunk/3rdparty/srs-bench/, and benchmarks via srs_bench. Run the smallest relevant test first, then the full suite required by the parent development workflow.

Can I search the whole repository when the router has no matching route?▼

No. If no route covers the task, the Skill reports that the code router does not cover it rather than discovering a new route ad hoc. Broad greps of repository roots like trunk/src/ or oryx/platform/ are explicitly forbidden.