Ocyss/srs-auth / .agents/skills/srs-develop
srs-develop
VerifiedDevelop, 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.
references/scan-prs.md
View on GitHub# Scan PRs
**Prerequisite:** Use this workflow only after the Task Router in `skills/srs-develop/SKILL.md` selects **Scan PRs**. Do not execute it directly.
1. Select exactly one pull-request repository: `ossrs/srs` or `ossrs/oryx`. Use an explicit URL, product name, or established task context; ask when ambiguous.
2. Prefer a pull request ID or URL from the user and scan only that pull request. If none is provided, scan only the single open pull request with the newest GitHub `updated_at` in the selected repository. Do not bulk-scan multiple pull requests.
3. Read the complete body, commit history, code diff, comments, reviews and review threads, and checks. Do not rely on labels, review state, or the author's summary. Use the selected project's documentation and code map to inspect only the relevant current code.
4. Assess the pull request from that complete current state. Look for correctness problems, regressions, compatibility impact, missing tests or documentation, unresolved feedback, and failing or incomplete checks.
5. Return the repository, pull request link, change summary, latest meaningful activity, checks and review state, findings, and one-line reason it needs maintainer attention.
Pull requests have no Truth Record. Do not invent one or treat any comment, review, or summary as authoritative; reconcile every source with the code change and current project state.
Do not modify, comment on, or submit reviews for pull requests.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |