'fix' 검색 결과

Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify remediation of a reported vulnerability
• Check for bypasses around a security fix
• Verify a fix after code moves or refactoring

Interpret n8n validation results and fix configuration, connection, and expression issues. Distinguish blocking errors from warnings and known false positives, choose suitable validation settings, review automatic fixes, and test actual outputs after structural checks pass.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand and fix workflow validation errors
• Distinguish known false positives from real warnings
• Preview and select automatic workflow fixes

Drive a failing GitHub Actions run to green in as few CI runs as possible, with a bounded fix-critique-commit-push-recheck loop that batches every evidenced fix into each push. Use when the user supplies a GitHub Actions run URL or run ID and wants the failure fixed, or asks to "make CI green", "fix the failing workflow/build/tests", "fix the red build", or to keep iterating on a branch or pull request until its checks pass. Pulls run results and failed-job logs through the gh CLI, and sends every fix plan to the rubber-duck reviewer before any code is touched.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Iteratively detects and auto-fixes technical debt in a codebase using three quality criteria from debt-analysis references: conditional branch simplification, encapsulation, and separation of concerns. Applies fixes directly to code, runs existing tests to verify no regressions, re-analyzes, and loops until all high-severity issues are resolved or max iterations (5) reached. Use this skill when you want to automatically improve code quality with real code changes, reduce technical debt systematically, or clean up code to meet quality standards. Trigger on phrases like "fix technical debt", "clean up code quality", "refactor and fix issues", "improve code quality automatically", "apply debt fixes", "fix code problems", "eliminate debt".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Audit and repair existing Cypress tests that fail intermittently. The skill identifies fixed delays, fragile command chains, shared state, and version compatibility issues, then guides targeted changes and repeated test runs to check the results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating Cypress tests that fail only in CI
• Replacing fixed delays with meaningful conditions
• Diagnosing detached DOM errors

Review and refine source-code comments and documentation attached to functions or other declarations. The skill removes redundant explanations, checks outdated TODOs, and preserves concise, evidence-based reasons and constraints that maintainers cannot readily infer from the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Cleaning up redundant code comments
• Reviewing TODO and FIXME markers
• Checking documentation when changing code

Assess skills CLI pull requests, or proposed code changes, for focused bug fixes supported by visible evidence and regression tests. Label qualifying candidates, suggest matching issues when appropriate, and leave a concise maintainer handoff.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identify bug fixes with evidence and regression tests
• Check whether a fix preserves other supported agents
• Find potentially matching issues missing from a pull request

Analyze NetFlow v9 and IPFIX records, which summarize network connections, to spot traffic spikes, scanning, unusual outbound transfers, and periodic connections. Compare traffic against normal patterns and produce a prioritized findings report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating sudden increases in network traffic
• Checking unusual outbound transfers for possible data theft
• Finding periodic connections to external control servers

Fix a small formatting bug in a credit note shell script while keeping the output label as credit and the amount positive. Run the specified targeted test and summarize the bug, fix, and verification command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix a credit note output formatting bug
• Check the credit label and positive amount
• Run the specified test and report the fix

Repair an entire broken feature by mapping its files and dependencies, checking configuration and logs, and confirming root causes. Apply fixes in sequence, then test the feature and the code that uses it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Repairing a broken feature from start to finish
• Investigating imports and configuration together
• Finding root causes across multiple modules

Interpret n8n validation results and work through fixes for missing settings, broken references, and expression errors. Distinguishes blocking errors from advisory warnings, explains validation profiles, and guides review of automatic fixes and execution failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding validation errors
• Deciding which warnings need attention
• Choosing a validation profile

Helps address Google Cloud Security Command Center findings by planning targeted fixes for permissions, misconfigurations, vulnerabilities, and combined attack paths. It includes impact checks, verification, rollback steps, and execution after user approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix excessive permissions flagged by Security Command Center
• Plan fixes for exposed buckets or firewall rules
• Address attack paths involving multiple security issues

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Investigate and fix production errors reported in Sentry through MCP, a connection to external tools. Analyze error details and execution history, check them against source code, implement fixes, and verify them with tests and regression checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a specific Sentry issue
• Finding the root cause of production exceptions
• Working through unresolved errors with fixes and tests

Runs repeated reviews and fixes on a Claude Code skill until no critical or major findings remain. Tracks findings across rounds, checks change boundaries, and stops for a design decision when fixes stop making progress.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refining a skill until critical and major findings are resolved
• Improving skill metadata, trigger descriptions, and references
• Tracking recurring findings across review rounds

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Investigate failing GitHub Actions checks on a pull request using the GitHub CLI. The skill gathers logs, summarizes failures, and proposes a fix plan, then implements changes only after explicit approval and reports changes and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating failed GitHub Actions checks on a pull request
• Summarizing error logs and proposing a fix plan
• Implementing an approved fix and reporting test results

Apply a specific set of Rails conventions to design, implementation, and code review. It keeps business logic in models, represents state changes as records, limits dependencies, and uses Minitest with fixtures, or predefined test data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing Rails models and database changes
• Representing state changes with separate records
• Reviewing code for consistent Rails conventions

Inspect a running website at different screen sizes to find layout problems, inconsistent styling, and accessibility issues such as poor contrast. Fix the relevant source code, recheck the results, and report changes with before-and-after screenshots.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding and fixing broken mobile layouts
• Reviewing spacing, fonts, and color consistency
• Checking contrast and keyboard focus visibility

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "fix a bug with minimal changes", "analyze change scope for a bugfix", "find the minimal set of files to change", "do a focused bugfix", or "scope a minimal repair".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.