ckorhonen
5 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
ckorhonensecurity-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, then writes a concise actionable Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Covers STRIDE, PASTA, and attacker-goal-based methodologies, with modern considerations for AI/ML systems, cloud-native deployments, and supply chain threats.
- installazioni
- 1
- GitHub Stars
- 16
- Aggiornato
- 5 lug
ckorhonenhone:broken-windows-hunt
- Detects entropy signals in a codebase: stale TODOs, disabled tests, lint suppressions, commented-out code, dead imports, empty catch blocks, and deprecated API usage. Designed for daily runs to catch quality erosion early. Do NOT use for feature work, refactoring planning, or security audits.
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 26 set
ckorhonenhone:test-naming-audit
- Checks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.
- installazioni
- 1
- GitHub Stars
- 0
- Aggiornato
- 26 set
ckorhonenswe:change-validation-planner
- Plans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.
- installazioni
- 1
- GitHub Stars
- 3
- Aggiornato
- 26 set
ckorhonenswe: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 re
- installazioni
- 1
- GitHub Stars
- 3
- Aggiornato
- 26 set