fastapi-route-change
Skill0 starsChanged 4 months agoMITView on GitHub
Use when adding, renaming, or modifying this backend's FastAPI routes, dependencies, middleware, or response behavior.
We split this skill into the rules it gives an agent
5 rules. 3 are common, 0 are distinctive, and 2 are very specific to this project.
3
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 13
Keep route handlers thin; put behavior in the service / manager layer.
- Common: line 14
Use Pydantic models for public request/response shapes.
- Common: line 16
Never log full query payloads or identifiers that may be patient-derived (PHI).
- Very specific: line 17
Don't pair CORS allow_origins=* with allow_credentials=True.
- Very specific: line 18
Add / refresh route tests, then run make ci-local.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FastAPI Route Change
Follow AGENTS.md first.
Workflow
- Inspect neighboring route / service modules under
spliceailookup_link/and follow their structure. - Keep route handlers thin; put behavior in the service / manager layer.
- Use Pydantic models for public request/response shapes; validate identifiers (gene / variant / HGVS / build / accession) before calling upstream.
- The upstream base URL is a fixed config constant — never construct it from user input (SSRF).
- Never log full query payloads or identifiers that may be patient-derived (PHI); log correlation id + route + timings only.
- Don't pair CORS
allow_origins=*withallow_credentials=True. - Add / refresh route tests, then run
make ci-local.
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- berntpopp/hpo-link★ 196% same
- berntpopp/mgi-link★ 196% same
- berntpopp/stringdb-link★ 196% same
- berntpopp/clingen-link★ 096% same
- berntpopp/gencc-link★ 096% same
- berntpopp/gnomad-link★ 096% same
- berntpopp/hgnc-link★ 096% same
- berntpopp/mondo-link★ 096% same
- berntpopp/vep-link★ 096% same
Wrote their own version · 1
- berntpopp/gtex-link★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ci-failure-triageSkill
- code-quality-reviewSkill
- dependency-cve-sweepSkill
- fleet-standard-adoptionSkill
- mcp-tool-changeSkill
- release-readinessSkill
- security-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.