915건 · 관련도순
Review code changes for bugs, security risks, design issues, and test quality, then turn findings into specific, prioritized feedback. Use its checklists and comment templates to establish consistent review standards and support developer mentoring.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate bugs, failing tests, and unexpected behavior before proposing changes. Follow four stages to gather evidence, compare working examples, test a specific cause, and verify a focused fix with a test that reproduces the problem.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose bugs, intermittent failures, and performance regressions through structured logging and reproduction. It ranks possible causes with confidence scores, tests competing explanations, and reports whether the evidence proves the cause or leaves the diagnosis incomplete.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate bugs, crashes, and intermittent failures without changing code. Multiple agents examine evidence from different angles, then produce ranked possible causes, confidence levels, and the smallest steps needed to confirm the diagnosis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides binary exploitation techniques for CTF challenges. Use when you already have a vulnerable native target or service and need to turn memory corruption or low-level primitives into code execution or privilege escalation, such as buffer overflows, format strings, heap bugs, ROP, ret2libc, shellcode, kernel exploitation, seccomp bypass, sandbox escape, or Windows/Linux exploit chains. Do not use it when the main blocker is understanding what the binary does; use reverse engineering first. Do not use it for pure web bugs, disk or packet forensics, or standalone crypto/math challenges.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation. Use when something is broken, failing, throwing, intermittently wrong, or unexpectedly slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codebase reconnaissance agent for Bug Hunter. Maps architecture, identifies trust boundaries, classifies files by risk priority, and detects service boundaries. Does NOT find bugs — finds where bugs hide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a deep code review of files, modules, a diff, or a branch - finding security vulnerabilities (mapped to OWASP Top 10:2025), correctness bugs, performance problems, and maintainability issues - and returns severity-ranked findings with evidence and concrete fixes. Use when the user asks to review, audit, or sanity-check code, asks "is this safe", "what's wrong with this", "find bugs", or wants a security or performance pass before shipping. For posting line comments on a GitHub pull request, use git-pr-reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes, explains, debugs, and optimizes BI calculations - Power BI / Fabric DAX measures and calculated columns, Tableau calculated fields (FIXED/INCLUDE/EXCLUDE LOD expressions, table calculations), and Looker LookML measures, dimensions, and derived tables. Use it whenever the request involves DAX, CALCULATE, a Power BI measure, a Tableau calc or LOD, LookML, or a business metric such as YoY, YTD, rolling 12 months, running total, percent of total, distinct customers, ranking, new vs returning customers, closing balances, or basket analysis. Use it especially when someone says a measure "shows the wrong total", "is blank", "ignores my slicer/filter", "repeats the same value on every row", or "is slow" - those are filter context, context transition, LOD order-of-operations, or fanout bugs this skill is built to diagnose. Produces the formula, the context it evaluates in, and a hand-checkable test with expected numbers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining for bug analysis, or conduct empirical studies on software defects. Triggers when users ask to find bug-introducing commits, identify when a bug was introduced, trace bug origins, perform SZZ analysis, or analyze bug-fixing commits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.