메뉴
Map repository ownership and bus-factor risk for security-sensitive code using git history and structural hotspots.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Implement async service initialization, lifecycle startup, dependency graph ordering, concurrency-limited initializers, rollback/disposal on failure, idempotent initialization, and circular dependency handling for DI containers or resource registries.
Use when implementing incremental caches, cache invalidation, cache stats, cache summary, list/import/export/prune/clear cache CLI modes, or CLI side-effect/reporting paths where normal analysis output and diagnostic output must not interfere.
Use when implementing analyzer or linter suppression directives such as nosec, nosec-begin/nosec-end, nosec-next-line, noqa, ignore-next-line, disable/enable regions, per-rule selectors, inline comments, warning filters, or line-based suppression for multi-line AST statements and metrics.
Implement JSON Schema parsers with recursive $ref, $defs, dependencies, dependentRequired, dependentSchemas, if/then/else, anyOf/allOf composition, and deep enum/const equality without stack overflows or shallow-only tests.
Use when implementing static taint/dataflow analysis, interprocedural taint tracking, vulnerability analyzer plugins, Bandit-like checks, B620/B621/B622/B623/B624 rules, or source-to-sink rules for SQL injection, shell injection, path traversal, SSRF, XSS, request.args/form/cookies, sys.argv, input(), os.environ, import aliases, nested functions, f-strings, percent formatting, .format(), or Python walrus/NamedExpr propagation.
Implement multipart HTTP response parsing APIs with Content-Type boundary validation, MIME delimiter framing, CRLF/LF/CR streaming chunks, part headers, continuations, duplicate headers, DecodingError, StreamConsumed, sync iter_multipart, async aiter_multipart, and raw response stream closure.
SOC 직업 분류 기준
| name | security-ownership-map |
| description | Map repository ownership and bus-factor risk for security-sensitive code using git history and structural hotspots. |
Use this skill when the user wants a security-oriented ownership analysis grounded in repository history.
