Ownership Risk Map
技能 已验证 活跃Maps engineering ownership risk in a repository using repo evidence such as git history, churn, bus factor, CODEOWNERS coverage, test density, and orphaned or unclear-owner surfaces. Use when a user says `map ownership risk`, `find bus factor hotspots`, `which files look orphaned`, `high-change low-test areas`, or asks for a recurring maintenance pass that identifies risky surfaces before they become incidents. Do NOT use for org charts, HR ownership assignments, or generic maintainer lists without repo evidence.
To provide engineers with a clear, evidence-backed map of ownership risk within a repository, enabling proactive maintenance and identification of potential fragility before incidents occur.
功能
- Maps engineering ownership risk using repo evidence
- Analyzes git history, churn, and bus factor
- Assesses CODEOWNERS coverage and test density
- Identifies orphaned or unclear-owner surfaces
- Provides ranked output for recurring maintenance
使用场景
- When a user asks to map ownership risk in a repository.
- When a user wants to find bus factor hotspots.
- When identifying files or modules with unclear ownership.
- For running recurring maintenance passes to identify risky surfaces.
非目标
- Assigning people to teams or building org charts.
- Generic repo orientation without an ownership-risk goal.
- General bug hunting or refactor planning.
- Security audits not specifically focused on ownership risk.
Practical Utility
- info:Usage examplesWhile the README provides installation and development examples, the SKILL.md itself lacks specific end-to-end usage examples demonstrating input, invocation, and output for the ownership risk mapping.
- info:Edge casesThe SKILL.md mentions handling unknowns and missing evidence, but detailed documentation of specific failure modes, symptoms, and recovery steps is not explicitly provided.
安装
/plugin install swe-skills@ckorhonen-swe-skills质量评分
已验证类似扩展
Evolve Team
99Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern no longer fits, user feedback reveals workflow gaps, a specialized variant is needed alongside the original, or agents have been added or removed from the library affecting team composition.
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Sync Profiles
100用于在用户想要列出、创建、切换、删除、比较或检查配置同步配置文件时使用。
Using Git Worktrees
100在开始需要与当前工作区隔离的功能性工作，或在执行实现计划之前使用 - 通过原生工具或 git worktree 回退确保存在隔离的工作区。
Unslop Commit
100重写提交消息，使其听起来像一个严谨的程序员编写的。去除 AI/营销术语（“全面的解决方案”、“健壮的实现”、“利用”、“增强”、“无缝地”、“此提交...”）。保留 Conventional Commits 格式。主题 ≤72 个字符（目标 ≤50），祈使语气。仅当“为什么”在主题中不明显时才写正文。在用户说“人性化提交”、“去营销术语化提交消息”、“让这个提交听起来像人话”、“/unslop-commit”、“/commit”、“写一个提交”或粘贴草稿提交以供清理时使用。暂存更改时自动触发。
Rule Effectiveness Analysis
100Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.