Loading...
Loading...
Found 199 Skills
Augments Trailmark code graphs with external audit findings from SARIF static analysis results and weAudit annotation files. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, cross-referencing Semgrep or CodeQL findings with call graph data, or visualizing audit findings in the context of code structure.
Provides the complete, verified grep scan command library for auditing React codebases before a React 18.3.1 or React 19 upgrade. Use this skill whenever running a migration audit - for both the react18-auditor and react19-auditor agents. Contains every grep pattern needed to find deprecated APIs, removed APIs, unsafe lifecycle methods, batching vulnerabilities, test file issues, dependency conflicts, and React 19 specific removals. Always use this skill when writing audit scan commands - do not rely on memory for grep syntax, especially for the multi-line async setState patterns which require context flags.
Use when the user asks to investigate, audit, trace, or explain how a feature, issue, module, workflow, API, config, or behavior works across one or more codebase projects.
Audit a design proposal or diff against Exarchos's architectural invariants — event-sourcing integrity (INV-1), facade equivalence over shared dispatch core (INV-2), basileus-forward (INV-3), platform-agnosticity (INV-4), and agent-first interface design (INV-5a input ergonomics, INV-5b spec-aligned output contract, INV-5c Aspire-inspired control-plane verbs, INV-5d action discriminator pattern). Pairs with /axiom:backend-quality — this skill is project-specific (axiom is generic). Triggers: 'check invariants', 'design conformance', 'check #1118 / #1109', or /design-invariants.
Audit a codebase for dead code, unreachable branches, duplicated logic, and vestigial abstractions, then remove them safely with proof. Use to reduce sprawl, pay down tech debt, or clean up after a feature is retired or migrated.
[user] 저장소를 읽기 전용으로 감사하고, 다른 실행자나 `tk-prep`이 재사용할 수 있는 우선순위가 있는 근거 기반 `AUD-*` `finding`을 작성합니다.
Adopt better-result in an existing TypeScript codebase. Use for a repository-wide error-handling audit and proposal, or for implementing a named vertical slice with TaggedError and Result.
Audit a codebase for adherence to the Spectrum design system and React Spectrum S2 best practices. Use when a developer asks to audit, review, lint, or check a project for Spectrum/S2 correctness, configuration, styling, accessibility, or component-usage issues.
Read-only defect review of a codebase - deep context and business-rule capture, perspective-based sweeps (business logic, error handling, security, correctness, concurrency, data integrity, performance, config, test quality), reproduction of each finding, severity calibration, and a decision-ready audit report with recommended fixes that are described but never applied. The codebase is left byte-identical. Use this whenever findings are wanted without changes, such as "review this codebase", "audit it but do not touch anything", "code review", "PR review", "second opinion on this code", "security assessment", "due diligence", "is this safe to ship", "what is wrong with this code", "review only", "report only", "read-only review", "check it without changing anything". Use it equally for business-logic defects where nothing crashes but the result is wrong - a wrong total, discount, tax or balance, a skippable step, a replayable action, a quota that does not hold, a user seeing another user's data. Prefer this over anti-bug whenever the user wants a report rather than a repaired repo, when the code belongs to someone else, or when changes need approval first. If the user actually wants the bugs fixed, use anti-bug instead.
Reviews PR changes against issue technical details and acceptance criteria, posts concise outcomes to PR and issue tracker, and routes autonomous next steps.
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
Fast-track GTM value preview for new users. Runs gtm-analytics-audit and gtm-strategy back to back and outputs the top 5 tracking opportunities with business rationale and effort estimates. No implementation, no DOM changes. Just a clear answer to "what should I track and why". Trigger on - "quickstart", "what should I track", "show me tracking opportunities", "quick GTM overview", "I'm new to GTM", "where do I start".