security-ownership-map
Map repository ownership and bus-factor risk for security-sensitive code using git history and structural hotspots.
Source facts
- Repository
- Calvin-Corbett/thomas
- Last source activity
- September 9, 2026 at 02:49
- Detected SKILL.md language
- English
- Stars
- 4
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- security-ownership-map
- description
- Map repository ownership and bus-factor risk for security-sensitive code using git history and structural hotspots.
# Security Ownership Map
Use this skill when the user wants a security-oriented ownership analysis grounded in repository history.
## Workflow
1. Identify the security-sensitive parts of the repo and the ownership question being asked.
2. Use git history and file topology to map maintainers and concentration risk.
3. Highlight orphaned or weakly owned security-sensitive surfaces.
4. Export or summarize the ownership data in a usable operational format.
5. Call out the biggest bus-factor and stewardship risks directly.
## Rules
- Do not confuse recent edit frequency with true expertise.
- Keep security sensitivity explicit when presenting ownership data.
View on GitHub