[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-ckorhonen-incident-followup-audit-en":3,"guides-for-ckorhonen-incident-followup-audit":476,"similar-k179xtrxqhv48c992a5zz18bvx86m89q-en":477},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":238,"isFallback":230,"parentExtension":243,"providers":265,"relations":269,"repo":270,"tags":474,"workflow":475},1778683790179.7803,"k179xtrxqhv48c992a5zz18bvx86m89q",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"Audits post-incident engineering follow-through after a sev or incident to verify whether the durable follow-up happened: regression tests, monitors, docs, runbooks, ownership updates, tickets, rollback learnings, and remaining backlog. Use when a user asks whether incident follow-up is complete, what still needs to be done after a postmortem, or how to close the engineering loop. Do NOT use for live incident response, root-cause analysis, or a generic bug hunt unrelated to an incident.",{"claudeCode":12},"ckorhonen/swe-skills","incident-followup-audit","https://github.com/ckorhonen/swe-skills",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":222,"workflow":236},1778683966277.1963,"kn72esw0320tc5km6t195qamm986n6a2","en",{"checks":20,"evaluatedAt":189,"extensionSummary":190,"features":191,"nonGoals":197,"promptVersionExtension":202,"promptVersionScoring":203,"purpose":204,"rationale":205,"score":206,"summary":207,"tags":208,"targetMarket":215,"tier":216,"useCases":217},[21,26,29,33,37,41,46,49,53,57,61,64,67,70,74,77,80,83,85,87,91,95,98,102,105,108,111,114,117,120,124,127,131,135,138,141,144,147,151,154,157,160,162,164,167,171,175,179,182,186],{"category":22,"check":23,"severity":24,"summary":25},"Invocation","Precise Purpose","pass","The description clearly states the skill's purpose: auditing post-incident follow-through. It also explicitly defines when to use it and when not to use it, anchoring the task to incident follow-up and distinguishing it from live incident response or RCA.",{"category":22,"check":27,"severity":24,"summary":28},"Concise Frontmatter","The frontmatter is dense and self-contained, clearly stating the core capability and providing relevant trigger phrases within the character limit.",{"category":30,"check":31,"severity":24,"summary":32},"Documentation","Concise Body","The SKILL.md file is concise and delegates deeper material to separate files as needed, adhering to progressive disclosure principles.",{"category":34,"check":35,"severity":24,"summary":36},"Context","Progressive Disclosure","The skill's instructions are well-organized and appear to delegate deeper or bulk material appropriately, although specific separate files for bulk material were not observed in the provided snippet.",{"category":34,"check":38,"severity":39,"summary":40},"Forked exploration","not_applicable","This skill is primarily an audit and reporting tool, not a deep exploration or code review tool that would necessitate a forked context.",{"category":42,"check":43,"severity":44,"summary":45},"Practical Utility","Usage examples","info","The SKILL.md outlines the desired output structure and evidence types but does not provide concrete, copy-pasteable end-to-end examples of invocations and their claimed outputs.",{"category":42,"check":47,"severity":24,"summary":48},"Edge cases","The SKILL.md explicitly documents limitations and failure modes, such as when evidence is missing or inaccessible, and advises on conservative judgment and distinguishing proven work from planned work.",{"category":50,"check":51,"severity":39,"summary":52},"Code Execution","Tool Fallback","The skill does not appear to rely on any external MCP servers or custom tools; it functions as a standalone prompt-based skill.",{"category":54,"check":55,"severity":24,"summary":56},"Safety","Halt on unexpected state","The instructions emphasize staying evidence-led and conservative, marking work as unknown if unproven, which implicitly suggests halting on unexpected or missing state rather than proceeding without evidence.",{"category":58,"check":59,"severity":24,"summary":60},"Portability","Cross-skill coupling","The skill is self-contained and focuses on auditing incident follow-through based on provided evidence, without appearing to implicitly rely on other specific skills.",{"category":42,"check":62,"severity":24,"summary":63},"Problem relevance","The description clearly identifies the problem of verifying post-incident engineering follow-through and its associated tasks.",{"category":42,"check":65,"severity":24,"summary":66},"Unique selling proposition","The skill offers a specialized workflow for auditing incident follow-up, which goes beyond generic incident response or RCA, providing a specific value proposition.",{"category":42,"check":68,"severity":24,"summary":69},"Production readiness","The skill is designed to be used with existing incident artifacts and provides a structured approach to auditing, making it suitable for real workflows.",{"category":71,"check":72,"severity":24,"summary":73},"Scope","Single responsibility principle","The skill has a single, well-defined responsibility: auditing post-incident engineering follow-through.",{"category":71,"check":75,"severity":24,"summary":76},"Description quality","The description accurately reflects the skill's purpose, scope, and intended use cases, including clear do-not-use scenarios.",{"category":22,"check":78,"severity":39,"summary":79},"Scoped tools","This is a skill and does not expose discrete tools or commands.",{"category":30,"check":81,"severity":39,"summary":82},"Configuration & parameter reference","As a skill, it does not expose configurable parameters or options in the traditional sense.",{"category":71,"check":84,"severity":39,"summary":79},"Tool naming",{"category":71,"check":86,"severity":39,"summary":79},"Minimal I/O surface",{"category":88,"check":89,"severity":24,"summary":90},"License","License usability","The extension is licensed under the MIT license, as confirmed by the bundled LICENSE file.",{"category":92,"check":93,"severity":24,"summary":94},"Maintenance","Commit recency","The last commit was on May 9, 2026, which is within the last 3 months.",{"category":92,"check":96,"severity":39,"summary":97},"Dependency Management","The skill does not appear to have any third-party dependencies that require management.",{"category":99,"check":100,"severity":39,"summary":101},"Security","Secret Management","The skill does not handle or expose any secrets.",{"category":99,"check":103,"severity":24,"summary":104},"Injection","The skill operates on provided evidence and incident artifacts, and does not appear to load or execute external code or data that could be subject to injection.",{"category":99,"check":106,"severity":24,"summary":107},"Transitive Supply-Chain Grenades","The skill does not fetch remote content or execute external scripts at runtime; all its logic is contained within the bundle.",{"category":99,"check":109,"severity":24,"summary":110},"Sandbox Isolation","The skill operates as a prompt-based audit tool and does not interact with or modify files outside its intended scope or the project checkout.",{"category":99,"check":112,"severity":24,"summary":113},"Sandbox escape primitives","There are no indications of detached process spawns or deny-retry loops within the skill's logic.",{"category":99,"check":115,"severity":24,"summary":116},"Data Exfiltration","The skill focuses on analyzing provided incident data and does not exhibit any behavior that would exfiltrate confidential data.",{"category":99,"check":118,"severity":24,"summary":119},"Hidden Text Tricks","The bundled content and descriptions appear to be free of hidden-steering tricks, control characters, or invisible Unicode characters.",{"category":121,"check":122,"severity":24,"summary":123},"Hooks","Opaque code execution","The skill logic is presented in plain markdown and does not involve obfuscated code, base64 payloads, or runtime script fetching.",{"category":58,"check":125,"severity":24,"summary":126},"Structural Assumption","The skill requires a local repository checkout and access to incident artifacts, which are clearly stated preconditions, but it does not make assumptions about specific file layouts beyond that.",{"category":128,"check":129,"severity":24,"summary":130},"Trust","Issues Attention","There are 0 open issues and 0 closed issues in the last 90 days, indicating no active issues or a well-maintained state.",{"category":132,"check":133,"severity":24,"summary":134},"Versioning","Release Management","The `pushedAt` date indicates recent activity, and the presence of a `SKILL.md` file suggests a versioning mechanism is in place even without explicit versioning in the frontmatter.",{"category":50,"check":136,"severity":39,"summary":137},"Validation","As a skill, it does not have executable code with parameters or structured output that would require schema validation.",{"category":99,"check":139,"severity":24,"summary":140},"Unguarded Destructive Operations","The skill is purely analytical and does not perform any destructive operations.",{"category":50,"check":142,"severity":24,"summary":143},"Error Handling","The skill's instructions emphasize conservative judgment and explicitly state how to handle missing or inaccessible evidence (marking as unknown), indicating a fail-closed approach.",{"category":50,"check":145,"severity":39,"summary":146},"Logging","The skill is analytical and does not perform destructive actions or outbound calls that would necessitate local audit logging.",{"category":148,"check":149,"severity":39,"summary":150},"Compliance","GDPR","The skill operates on incident artifacts and code-related information, not personal data.",{"category":148,"check":152,"severity":24,"summary":153},"Target market","The skill's function is universal to software engineering incident follow-up and has no regional or jurisdictional limitations.",{"category":58,"check":155,"severity":24,"summary":156},"Runtime stability","The skill is prompt-based and does not make assumptions about specific editors, shells, or operating systems beyond requiring access to local incident artifacts.",{"category":30,"check":158,"severity":24,"summary":159},"README","The README file exists and provides a good overview of the repository's structure, conventions, and available skills.",{"category":71,"check":161,"severity":39,"summary":79},"Tool surface size",{"category":22,"check":163,"severity":39,"summary":79},"Overlapping near-synonym tools",{"category":30,"check":165,"severity":24,"summary":166},"Phantom features","All advertised features in the description and SKILL.md appear to be implemented as part of the skill's audit workflow.",{"category":168,"check":169,"severity":24,"summary":170},"Install","Installation instruction","The README provides clear installation instructions using `npx skills install` and the SKILL.md details the necessary inputs and evidence sources.",{"category":172,"check":173,"severity":24,"summary":174},"Errors","Actionable error messages","The instructions clearly outline how to handle missing or inaccessible evidence by marking it as 'unknown' and emphasize conservative judgment, providing a clear path for unexpected states.",{"category":176,"check":177,"severity":39,"summary":178},"Execution","Pinned dependencies","The skill does not appear to have executable scripts with dependencies that require pinning.",{"category":71,"check":180,"severity":39,"summary":181},"Dry-run preview","The skill is purely analytical and does not perform any state-changing operations or outbound calls.",{"category":183,"check":184,"severity":39,"summary":185},"Protocol","Idempotent retry & timeouts","The skill is prompt-based and does not involve remote calls or state-changing operations that would require idempotency or timeouts.",{"category":148,"check":187,"severity":39,"summary":188},"Telemetry opt-in","The skill does not emit any telemetry.",1778683966065,"This skill audits the completion of engineering tasks after a production incident, verifying follow-up actions such as regression tests, monitoring updates, documentation changes, and ticket resolution. It requires access to incident artifacts like postmortems and issue trackers to anchor its audit.",[192,193,194,195,196],"Audits post-incident engineering follow-through","Verifies durable follow-up actions","Identifies missing or incomplete work","Ranks remaining backlog by risk and impact","Anchors audit to specific incident identifiers",[198,199,200,201],"Live incident response or war-room triage","Root-cause analysis of the incident itself","Generic code review or bug hunting unrelated to an incident","Broad cleanup work not tied to a concrete incident or postmortem","3.0.0","4.4.0","To provide a structured audit of post-incident engineering follow-through, ensuring that all necessary follow-up actions are completed and closing the engineering loop after an incident.","High score due to comprehensive documentation, clear purpose, and robust security checks. Minor points deducted for lack of explicit end-to-end examples.",97,"A high-quality skill for auditing post-incident engineering follow-through with clear instructions and robust safety checks.",[209,210,211,212,213,214],"incident-management","audit","postmortem","engineering-follow-up","devops","reliability","global","verified",[218,219,220,221],"Audit postmortem follow-through after a sev or production incident","Check whether regression tests, monitors, runbooks, or docs were added","See whether ownership, tickets, or rollback learnings were captured","Review what is still left to do before an incident is considered fully closed",{"codeQuality":223,"collectedAt":225,"documentation":226,"maintenance":229,"security":233,"testCoverage":235},{"hasLockfile":224},true,1778683951202,{"descriptionLength":227,"readmeSize":228},491,8683,{"closedIssues90d":8,"forks":8,"hasChangelog":230,"openIssues90d":8,"pushedAt":231,"stars":232},false,1778361321000,1,{"hasNpmPackage":230,"license":234,"smitheryVerified":230},"MIT",{"hasCi":224,"hasTests":230},{"updatedAt":237},1778683966277,{"basePath":239,"githubOwner":240,"githubRepo":241,"locale":18,"slug":13,"type":242},"skills/incident-followup-audit","ckorhonen","swe-skills","skill",{"_creationTime":244,"_id":245,"community":246,"display":247,"identity":250,"parentExtension":253,"providers":254,"relations":260,"tags":262,"workflow":263},1778683790179.7788,"k17d2yq229g61qvea0x8t60w1h86mgr8",{"reviewCount":8},{"description":248,"installMethods":249,"name":241,"sourceUrl":14},"17 agent skills for engineering analysis and judgment — PR risk review, repo introspection, audits, ownership maps, refactor opportunities. See https://cdd.dev/skill/.",{"claudeCode":241},{"basePath":251,"githubOwner":240,"githubRepo":241,"locale":18,"slug":241,"type":252},"","plugin",null,{"extract":255},{"commitSha":256,"plugin":257},"HEAD",{"mcpCount":8,"provider":258,"skillCount":259},"classify",17,{"repoId":261},"kd7b5kvzw3q7dgvym5bdx3m53986mann",[],{"extractAt":264,"updatedAt":264},1778683790179,{"evaluate":266,"extract":268},{"promptVersionExtension":202,"promptVersionScoring":203,"score":206,"tags":267,"targetMarket":215,"tier":216},[209,210,211,212,213,214],{"commitSha":256},{"parentExtensionId":245,"repoId":261},{"_creationTime":271,"_id":261,"identity":272,"providers":273,"workflow":470},1778683785537.182,{"githubOwner":240,"githubRepo":241,"sourceUrl":14},{"classify":274,"discover":458,"github":461},{"commitSha":256,"extensions":275},[276,324,333,341,349,357,365,370,378,386,394,402,410,418,426,434,442,450],{"basePath":251,"description":248,"displayName":241,"installMethods":277,"rationale":278,"selectedPaths":279,"source":323,"sourceLanguage":18,"type":252},{"claudeCode":241},"plugin manifest at .claude-plugin/plugin.json",[280,283,285,288,291,293,295,297,299,301,303,305,307,309,311,313,315,317,319,321],{"path":281,"priority":282},".claude-plugin/plugin.json","mandatory",{"path":284,"priority":282},"README.md",{"path":286,"priority":287},"LICENSE","high",{"path":289,"priority":290},"skills/babysit-pr/SKILL.md","medium",{"path":292,"priority":290},"skills/capture-knowledge/SKILL.md",{"path":294,"priority":290},"skills/change-validation-planner/SKILL.md",{"path":296,"priority":290},"skills/create-skill/SKILL.md",{"path":298,"priority":290},"skills/docs-drift-audit/SKILL.md",{"path":300,"priority":290},"skills/incident-followup-audit/SKILL.md",{"path":302,"priority":290},"skills/init/SKILL.md",{"path":304,"priority":290},"skills/merged-pr-monitoring/SKILL.md",{"path":306,"priority":290},"skills/observability-gap-hunt/SKILL.md",{"path":308,"priority":290},"skills/ownership-risk-map/SKILL.md",{"path":310,"priority":290},"skills/performance-hunt/SKILL.md",{"path":312,"priority":290},"skills/pr-risk-review/SKILL.md",{"path":314,"priority":290},"skills/recent-commit-bug-hunt/SKILL.md",{"path":316,"priority":290},"skills/refactor-opportunities/SKILL.md",{"path":318,"priority":290},"skills/repo-introspection/SKILL.md",{"path":320,"priority":290},"skills/security-audit/SKILL.md",{"path":322,"priority":290},"skills/test-gap-hunt/SKILL.md","rule",{"basePath":325,"description":326,"displayName":327,"installMethods":328,"rationale":329,"selectedPaths":330,"source":323,"sourceLanguage":18,"type":242},"skills/babysit-pr","Babysits an open pull request end-to-end by polling every minute, triaging new comments and reviews, handling CI failures, iterating on reviewer scores, and stopping only when the PR is ready to merge. Use when a user says `babysit this PR`, `watch this PR until it's merge-ready`, `handle review feedback on my PR`, or `keep iterating on this PR until reviewers are happy`. Do NOT use for a one-shot PR risk review, merged PR production monitoring, or repo-wide CI debugging with no scoped PR.","babysit-pr",{"claudeCode":12},"SKILL.md frontmatter at skills/babysit-pr/SKILL.md",[331],{"path":332,"priority":282},"SKILL.md",{"basePath":334,"description":335,"displayName":336,"installMethods":337,"rationale":338,"selectedPaths":339,"source":323,"sourceLanguage":18,"type":242},"skills/capture-knowledge","Audits a repository's code and docs to find important conventions, workflows, and architectural decisions that are missing from agent-facing guidance, then drafts review-ready updates. Use when a user says `capture repo knowledge`, `document implicit conventions`, `turn repo patterns into agent rules`, or asks what future agents should remember about a codebase. Do NOT use for a generic repo tour, onboarding walkthrough, or architecture summary that does not need reusable guidance updates.","capture-knowledge",{"claudeCode":12},"SKILL.md frontmatter at skills/capture-knowledge/SKILL.md",[340],{"path":332,"priority":282},{"basePath":342,"description":343,"displayName":344,"installMethods":345,"rationale":346,"selectedPaths":347,"source":323,"sourceLanguage":18,"type":242},"skills/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.","change-validation-planner",{"claudeCode":12},"SKILL.md frontmatter at skills/change-validation-planner/SKILL.md",[348],{"path":332,"priority":282},{"basePath":350,"description":351,"displayName":352,"installMethods":353,"rationale":354,"selectedPaths":355,"source":323,"sourceLanguage":18,"type":242},"skills/create-skill","Creates or revises `swe:` skills for this repository using a repeatable authoring workflow: define concrete use cases, tune trigger boundaries, apply progressive disclosure, add matching eval assets, and validate the package. Use when adding a new skill, tightening an existing skill that over- or under-triggers, or distilling an external workflow into a repo-ready skill. Do NOT use for generic documentation edits or for executing the workflow the skill would describe.","create-skill",{"claudeCode":12},"SKILL.md frontmatter at skills/create-skill/SKILL.md",[356],{"path":332,"priority":282},{"basePath":358,"description":359,"displayName":360,"installMethods":361,"rationale":362,"selectedPaths":363,"source":323,"sourceLanguage":18,"type":242},"skills/docs-drift-audit","Audits a repository for human-facing or operational documentation that drifted from code, config, interfaces, workflows, or repo structure changes. Use when a user says `check docs drift`, `docs are stale`, `update the runbook after this change`, or `what documentation is missing after this change`. Do NOT use for agent-guidance updates, generic documentation rewrites, or writing docs without evidence that they are stale.","docs-drift-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/docs-drift-audit/SKILL.md",[364],{"path":332,"priority":282},{"basePath":239,"description":10,"displayName":13,"installMethods":366,"rationale":367,"selectedPaths":368,"source":323,"sourceLanguage":18,"type":242},{"claudeCode":12},"SKILL.md frontmatter at skills/incident-followup-audit/SKILL.md",[369],{"path":332,"priority":282},{"basePath":371,"description":372,"displayName":373,"installMethods":374,"rationale":375,"selectedPaths":376,"source":323,"sourceLanguage":18,"type":242},"skills/init","Initializes an optional repo-local agent collaboration preference file at `.ai/swe.json` by running a short interview or a zero-question quick mode. Use when a user says `initialize agent settings for this repo`, `set up my local agent prefs here`, `run quick init for this project`, or `create .ai/swe.json for how I like to work`. Do NOT use for `npm init`, project scaffolding, dependency installation, or environment bootstrap.","init",{"claudeCode":12},"SKILL.md frontmatter at skills/init/SKILL.md",[377],{"path":332,"priority":282},{"basePath":379,"description":380,"displayName":381,"installMethods":382,"rationale":383,"selectedPaths":384,"source":323,"sourceLanguage":18,"type":242},"skills/merged-pr-monitoring","Reviews recently merged pull requests, confirms whether they reached production, compares pre- and post-deploy signals, and summarizes observable impact. Use when a user says `monitor merged PRs`, `did this deploy hurt prod`, `check production impact of yesterday's merges`, or asks for a post-deploy readout tied to merged GitHub PRs. Do NOT use for a pre-merge code review, incident analysis with no PR scope, or generic dashboard triage disconnected from merged changes.","merged-pr-monitoring",{"claudeCode":12},"SKILL.md frontmatter at skills/merged-pr-monitoring/SKILL.md",[385],{"path":332,"priority":282},{"basePath":387,"description":388,"displayName":389,"installMethods":390,"rationale":391,"selectedPaths":392,"source":323,"sourceLanguage":18,"type":242},"skills/observability-gap-hunt","Inspects services, jobs, and code paths for missing or weak logs, metrics, traces, alerts, dashboards, or deployment-linked telemetry, then returns a tightly scoped backlog of observability gaps. Use when a user says `find observability gaps`, `audit telemetry coverage`, `what logs or metrics are missing`, `check alerting coverage`, or asks for a recurring telemetry review. Do NOT use for live incident response, root-cause analysis, generic performance tuning, or a broad code review.","observability-gap-hunt",{"claudeCode":12},"SKILL.md frontmatter at skills/observability-gap-hunt/SKILL.md",[393],{"path":332,"priority":282},{"basePath":395,"description":396,"displayName":397,"installMethods":398,"rationale":399,"selectedPaths":400,"source":323,"sourceLanguage":18,"type":242},"skills/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.","ownership-risk-map",{"claudeCode":12},"SKILL.md frontmatter at skills/ownership-risk-map/SKILL.md",[401],{"path":332,"priority":282},{"basePath":403,"description":404,"displayName":405,"installMethods":406,"rationale":407,"selectedPaths":408,"source":323,"sourceLanguage":18,"type":242},"skills/performance-hunt","Hunts for concrete performance bottlenecks in a scoped repository surface using profiler output, benchmarks, query plans, traces, bundle analysis, or repo evidence, then returns the smallest high-value follow-up experiments or fixes. Use when a user says `find performance bottlenecks`, `why is this slow`, `profile this flow`, `hunt hot paths`, or asks for a recurring performance review. Do NOT use for live incident response, generic observability audits, speculative micro-optimization, or broad architecture rewrites with no bottleneck evidence.","performance-hunt",{"claudeCode":12},"SKILL.md frontmatter at skills/performance-hunt/SKILL.md",[409],{"path":332,"priority":282},{"basePath":411,"description":412,"displayName":413,"installMethods":414,"rationale":415,"selectedPaths":416,"source":323,"sourceLanguage":18,"type":242},"skills/pr-risk-review","Reviews open or draft pull requests for engineering risk before merge, focusing on missing validation, hidden coupling, rollout and rollback gaps, migrations, feature flags, and other agent-safe next actions. Use when a user says `review this PR for risk`, `pre-merge review`, `is this PR safe to merge`, or asks for a risk-focused PR review. Do NOT use for post-merge production monitoring, broad code smell review, or commit-scoped bug hunting.","pr-risk-review",{"claudeCode":12},"SKILL.md frontmatter at skills/pr-risk-review/SKILL.md",[417],{"path":332,"priority":282},{"basePath":419,"description":420,"displayName":421,"installMethods":422,"rationale":423,"selectedPaths":424,"source":323,"sourceLanguage":18,"type":242},"skills/recent-commit-bug-hunt","Scans recent commits in one or more repositories, identifies likely bugs using concrete repo evidence only, and proposes tightly scoped remediation sessions. Use when a user says `scan recent commits for bugs`, `what did I probably break`, `review yesterday's changes for regressions`, or asks for a commit-scoped bug hunt. Do NOT use for a broad code health review, full security audit, or speculative bug hunting with no repo or time scope.","recent-commit-bug-hunt",{"claudeCode":12},"SKILL.md frontmatter at skills/recent-commit-bug-hunt/SKILL.md",[425],{"path":332,"priority":282},{"basePath":427,"description":428,"displayName":429,"installMethods":430,"rationale":431,"selectedPaths":432,"source":323,"sourceLanguage":18,"type":242},"skills/refactor-opportunities","Reviews a repository and returns a short, best-first backlog of small, low-risk refactor tickets with clear write boundaries and validation paths. Use when a user says `find refactor opportunities`, `what small cleanup tickets should we hand to agents`, `give me parallelizable refactors`, or asks for narrow maintainability wins in an existing repo. Do NOT use for a broad architecture redesign, style-only cleanup sweep, or bug hunt focused on functional regressions.","refactor-opportunities",{"claudeCode":12},"SKILL.md frontmatter at skills/refactor-opportunities/SKILL.md",[433],{"path":332,"priority":282},{"basePath":435,"description":436,"displayName":437,"installMethods":438,"rationale":439,"selectedPaths":440,"source":323,"sourceLanguage":18,"type":242},"skills/repo-introspection","Inspects an unfamiliar software repository and produces a concrete orientation report covering structure, tooling, entry points, boundaries, active surfaces, and safe places to start work. Use when a user says `help me understand this repo`, `map this codebase before I edit it`, `where should I start`, or asks for an engineering walkthrough before planning or delegation. Do NOT use when the user already knows the target change and wants implementation, or when they need a specific bug diagnosis rather than repo orientation.","repo-introspection",{"claudeCode":12},"SKILL.md frontmatter at skills/repo-introspection/SKILL.md",[441],{"path":332,"priority":282},{"basePath":443,"description":444,"displayName":445,"installMethods":446,"rationale":447,"selectedPaths":448,"source":323,"sourceLanguage":18,"type":242},"skills/security-audit","Audits a repository, workspace, or monorepo for dependency vulnerabilities, outdated security-sensitive packages, license issues, and dependency hygiene gaps, then compiles one evidence-backed report. Use when a user says `run a security audit`, `check dependencies and licenses`, `audit this monorepo for vulnerable packages`, or asks for a package-level security review. Do NOT use for a general secure-code review, threat model, or speculative vulnerability hunt without manifests, lockfiles, or package surfaces to inspect.","security-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/security-audit/SKILL.md",[449],{"path":332,"priority":282},{"basePath":451,"description":452,"displayName":453,"installMethods":454,"rationale":455,"selectedPaths":456,"source":323,"sourceLanguage":18,"type":242},"skills/test-gap-hunt","Identifies and prioritizes the highest-value test coverage gaps in a repository or workspace, then incrementally adds or strengthens tests using the local test stack and cleanly scoped subagent work when available. Use when a user says `improve test coverage`, `find weak tests`, `add missing test cases`, `run a recurring test-improvement pass`, or asks for a language-agnostic workflow to strengthen mocks, fixtures, and test structure without chasing raw coverage numbers. Do NOT use for first-time framework selection, broad test-stack migrations, or large production refactors.","test-gap-hunt",{"claudeCode":12},"SKILL.md frontmatter at skills/test-gap-hunt/SKILL.md",[457],{"path":332,"priority":282},{"sources":459},[460],"manual",{"closedIssues90d":8,"description":462,"forks":8,"homepage":463,"license":234,"openIssues90d":8,"pushedAt":231,"readmeSize":228,"stars":232,"topics":464},"Claude Code skills for on-demand engineering work — PR risk review, repo introspection, audits, ownership maps. Published at cdd.dev/skills/swe.","https://cdd.dev/skills/swe/",[465,466,467,468,469],"agent-skills","claude-code","claude-plugins","code-review","codex",{"classifiedAt":471,"discoverAt":472,"extractAt":473,"githubAt":473,"updatedAt":471},1778683789715,1778683785537,1778683787839,[210,213,212,209,211,214],{"evaluatedAt":237,"extractAt":264,"updatedAt":237},[],[478,508,534,564,584,613],{"_creationTime":479,"_id":480,"community":481,"display":482,"identity":488,"providers":492,"relations":501,"tags":504,"workflow":505},1778675056600.2393,"k17ct63reqgdem6s75y0b76kn186m8xs",{"reviewCount":8},{"description":483,"installMethods":484,"name":486,"sourceUrl":487},"Pre-production audit that scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI/CD setup or infra provisioning.\n",{"claudeCode":485},"alirezarezvani/claude-skills","ship-gate","https://github.com/alirezarezvani/claude-skills",{"basePath":489,"githubOwner":490,"githubRepo":491,"locale":18,"slug":486,"type":242},"engineering/skills/ship-gate","alirezarezvani","claude-skills",{"evaluate":493,"extract":500},{"promptVersionExtension":202,"promptVersionScoring":203,"score":494,"tags":495,"targetMarket":215,"tier":216},100,[496,497,498,210,499,213],"security","code-quality","deployment","checklist",{"commitSha":256,"license":234},{"parentExtensionId":502,"repoId":503},"k173223hfbd6c4mx6r1jdx23wn86mbpb","kd7ff9s1w43mfyy1n7hf87816186m6px",[210,499,497,498,213,496],{"evaluatedAt":506,"extractAt":507,"updatedAt":506},1778679066333,1778675056600,{"_creationTime":509,"_id":510,"community":511,"display":512,"identity":518,"providers":521,"relations":528,"tags":530,"workflow":531},1778696113180.8176,"k17cph4pqw00c8x14hpx2s42xd86m0c2",{"reviewCount":8},{"description":513,"installMethods":514,"name":516,"sourceUrl":517},"Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.",{"claudeCode":515},"rampstackco/claude-skills","incident-response","https://github.com/rampstackco/claude-skills",{"basePath":519,"githubOwner":520,"githubRepo":491,"locale":18,"slug":516,"type":242},"skills/incident-response","rampstackco",{"evaluate":522,"extract":527},{"promptVersionExtension":202,"promptVersionScoring":203,"score":494,"tags":523,"targetMarket":215,"tier":216},[209,524,213,525,526],"operations","production","on-call",{"commitSha":256},{"repoId":529},"kd7bebccrrd1xf6w868aggftrd86m86v",[213,209,526,524,525],{"evaluatedAt":532,"extractAt":533,"updatedAt":532},1778697024409,1778696113180,{"_creationTime":535,"_id":536,"community":537,"display":538,"identity":544,"providers":548,"relations":557,"tags":560,"workflow":561},1778692306427.0989,"k1796t5tyzzwfm2x9bbbaaw5y586ndfk",{"reviewCount":8},{"description":539,"installMethods":540,"name":542,"sourceUrl":543},"Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.",{"claudeCode":541},"Lifecycle-Innovations-Limited/claude-ops","ops-fires","https://github.com/Lifecycle-Innovations-Limited/claude-ops",{"basePath":545,"githubOwner":546,"githubRepo":547,"locale":18,"slug":542,"type":242},"claude-ops/skills/ops-fires","Lifecycle-Innovations-Limited","claude-ops",{"evaluate":549,"extract":556},{"promptVersionExtension":202,"promptVersionScoring":203,"score":494,"tags":550,"targetMarket":215,"tier":216},[209,551,213,552,553,554,555],"monitoring","automation","aws","sentry","ci-cd",{"commitSha":256},{"parentExtensionId":558,"repoId":559},"k17d0t6ns7y6t377pfprg128hd86nm89","kd7d52tcek2e34r805zs06b10d86n39v",[552,553,555,213,209,551,554],{"evaluatedAt":562,"extractAt":563,"updatedAt":562},1778692547909,1778692306427,{"_creationTime":565,"_id":566,"community":567,"display":568,"identity":572,"providers":574,"relations":580,"tags":581,"workflow":582},1778696113180.8066,"k17ad4da3hgtxbv0bf8a1xea1986mkrj",{"reviewCount":8},{"description":569,"installMethods":570,"name":571,"sourceUrl":517},"Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.",{"claudeCode":515},"after-action-report",{"basePath":573,"githubOwner":520,"githubRepo":491,"locale":18,"slug":571,"type":242},"skills/after-action-report",{"evaluate":575,"extract":579},{"promptVersionExtension":202,"promptVersionScoring":203,"score":494,"tags":576,"targetMarket":215,"tier":216},[211,577,524,578,209],"retrospective","documentation",{"commitSha":256},{"repoId":529},[578,209,524,211,577],{"evaluatedAt":583,"extractAt":533,"updatedAt":583},1778696189739,{"_creationTime":585,"_id":586,"community":587,"display":588,"identity":594,"providers":598,"relations":606,"tags":609,"workflow":610},1778691344230.1392,"k17bmxwpjrkj840wfkmddqb6td86nh7d",{"reviewCount":8},{"description":589,"installMethods":590,"name":592,"sourceUrl":593},"Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.",{"claudeCode":591},"jeffallan/claude-skills","SRE Engineer","https://github.com/jeffallan/claude-skills",{"basePath":595,"githubOwner":596,"githubRepo":491,"locale":18,"slug":597,"type":242},"skills/sre-engineer","jeffallan","sre-engineer",{"evaluate":599,"extract":605},{"promptVersionExtension":202,"promptVersionScoring":203,"score":600,"tags":601,"targetMarket":215,"tier":216},98,[602,213,214,551,552,209,603,604],"sre","slo","error-budget",{"commitSha":256,"license":234},{"parentExtensionId":607,"repoId":608},"k177fx0q0bsftkws6j1av221j186ndt6","kd77w37et655xneae33d1p2d2n86ncxp",[552,213,604,209,551,214,603,602],{"evaluatedAt":611,"extractAt":612,"updatedAt":611},1778692728000,1778691344230,{"_creationTime":614,"_id":615,"community":616,"display":617,"identity":621,"providers":623,"relations":629,"tags":631,"workflow":632},1778675056600.2476,"k17632wybnqfztvzcyktzm7z6x86m8eg",{"reviewCount":8},{"description":618,"installMethods":619,"name":620,"sourceUrl":487},"Incident Commander Skill",{"claudeCode":485},"incident-commander",{"basePath":622,"githubOwner":490,"githubRepo":491,"locale":18,"slug":620,"type":242},"engineering-team/skills/incident-commander",{"evaluate":624,"extract":628},{"promptVersionExtension":202,"promptVersionScoring":203,"score":600,"tags":625,"targetMarket":215,"tier":216},[209,602,213,211,552,626,627],"reporting","python",{"commitSha":256},{"parentExtensionId":630,"repoId":503},"k179s2ynpr6g927zdzf23zrhad86net8",[552,213,209,211,627,626,602],{"evaluatedAt":633,"extractAt":507,"updatedAt":633},1778683247698]