Menu
Use when answering QUIC protocol or RFC questions in this repository, especially section lookups, frames, transport parameters, ACK behavior, version negotiation, packet formats, error codes, or when grounded RFC citations are needed.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement CoQUIC GitHub issues end to end. Use when the user gives a GitHub issue URL/number or asks to fetch, implement, test, add Duvet/RFC annotations, update issue TODO checkboxes, comment on, or close an implementation issue in the minhuw/coquic repository.
Create consistent GitHub issues for tracking implementation work, bug fixes, design tasks, technical debt, protocol gaps, test gaps, performance work, documentation work, CI failures, interop follow-ups, and investigations in the coquic repository. Use when asked to draft, create, batch-create, organize, or update GitHub issues for things that should be fixed, implemented, reviewed later, or tracked as project work.
Fetch and fix current CodeQL and Codacy issues for the minhuw/coquic repository. Use when asked to inspect GitHub Security code scanning alerts at https://github.com/minhuw/coquic/security, Codacy current issues at https://app.codacy.com/gh/minhuw/coquic/issues/current, or to automatically repair static-analysis/security findings without weakening scanner configuration.
Debug failed remote GitHub Actions Interop workflow runs for the coquic repository. Use when given a .github/workflows/interop.yml run URL or run ID and asked to inspect CI, download failed interop logs/artifacts with gh, identify failed peer/testcase/direction combinations, reproduce them locally with interop/run-official.sh, fix reproducible coquic bugs, validate, commit, push, and dispatch a fresh Interop workflow run.
| name | quic-rag |
| description | Use when answering QUIC protocol or RFC questions in this repository, especially section lookups, frames, transport parameters, ACK behavior, version negotiation, packet formats, error codes, or when grounded RFC citations are needed. |
Use the repo-local QUIC specification knowledge base before answering protocol
questions in coquic.
nix run .#qdrant-dev -- statusrag/scripts/query-rag doctor --state-dir .ragnix run .#qdrant-dev -- start and retry once.rag/scripts/query-rag get-section --doc rfc9000 --section-id 18.2rag/scripts/query-rag get-section --doc draft-ietf-quic-qlog-main-schema-13 --section-id 1rag/scripts/query-rag trace-term max_udp_payload_sizerag/scripts/query-rag lookup-term --term-type transport_parameter --name max_udp_payload_sizerag/scripts/query-rag related-sections --doc rfc9369 --section-id 5rag/scripts/query-rag search-sections "ACK frame behavior" --top-k 5rag/scripts/build-index --source <source-dir> --state-dir .rag.