'fix' 검색 결과

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

Diagnose and fix slow pyfixest regression GRIDS (many feols/fepois calls run sequentially) that stay slow despite demeaner_backend="cupy64" and an idle GPU. Use when: (1) a script looping dozens of pf.feols models on a 100k+ row panel takes ~1 min/model, (2) process inspection shows ~1-1.5 cores busy and nvidia-smi shows ~0% GPU utilization with a resident cupy context, (3) planning any worker prompt that will run a model grid (robustness variants x FE structures x domains). Root cause: per-model CPU-side single-threaded fixed costs (formulaic model-matrix build, interaction construction, singleton detection, cluster vcov) dominate wall time; GPU demeaning is a small slice. Fix: shard the model grid across OS processes and/or use pyfixest multiple-estimation syntax; mandate this IN THE WORKER PROMPT.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

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

Investigate and fix failing CI. Takes a PR reference, one or more CI run/job URLs, or freeform text describing where the failures are, then enumerates failing workflows/jobs/steps, determines the root cause (often one shared cause behind several red checks), proposes a fix plan, applies code changes, commits, pushes, watches the new runs, and repeats until checks pass. Use when the user says "fix CI", "CI is red", "checks are failing", "the build is broken on my PR", "fix the failing jobs", or pastes a failing CI run URL. Do NOT use for authoring new workflows, or for read-only diagnosis with no fix intent — use gha-log-reader for that.

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

copy_tuner（CopyTuner / copy_tuner_client）の全 i18n キーを config/locales へ prefix 単位で移行し終えた後、 gem・初期化子・CI・deploy・ドキュメント・MCP 設定を一括撤去して copy_tuner 依存を完全に取り除くスキル。 prefix 単位の移行は copy-tuner-to-locales-migrate-prefix スキルで先に完了させておくこと。

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

Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.

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

MSBuild property definition patterns: conditional defaults, composition/concatenation, path normalization, trailing slash handling, TFM detection helpers, and property evaluation order. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing MSBuild property definition issues in .props or .csproj files, reviewing and fixing shared property configuration anti-patterns, fixing DefineConstants or NoWarn being overwritten instead of appended, fixing unconditional property assignments that prevent project-level overrides, fixing unquoted conditions that fail when properties are empty, fixing hardcoded paths that break cross-platform builds, setting property defaults that can be overridden, understanding property evaluation order and last-write-wins semantics. DO NOT USE FOR: props vs targets placement (use directory-build-organization), item operations (use item-management), target structure (use target-authoring), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

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

Adversarial triage of open review findings on a PR. Every finding (Codex, Claude bot, Gemini) is a hostile hypothesis to REFUTE — fix only what is proven real, reachable, in the PR's scope, and above the round's severity bar. The bar rises every review round. Everything else is declined or filed as an issue. Use for 'fix the PR findings', '/fix', '/fix 123', or before any fix commit in a review loop.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

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

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

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

로컬 실행이나 지속적 통합에서 발견한 Python 타입 검사 오류를 분류하고, 타입 좁히기와 주석 수정부터 재검증까지 진행합니다. 새로운 타입 검사 범위 추가도 다룹니다.

• 지속적 통합의 타입 검사 실패 수정
• None이 포함된 타입 오류 수정
• 타입 검사 대상 디렉터리 추가

iOS 앱의 버그에 대해 소스 수정, 재빌드, 실제 기기 재배포와 수정 확인까지 수행합니다. 같은 문제의 재발을 감지할 수 있도록 상태 스냅샷도 테스트 데이터로 남깁니다.

• /ios-qa가 보고한 버그 수정
• 재빌드와 재배포 후 수정 결과 확인
• 회귀 테스트용 상태 스냅샷 저장

Paperclip의 느린 PostgreSQL 쿼리를 조사하고 수정합니다. 로컬에서 속도와 결과 일치를 검증하고 회귀 테스트 및 검사 결과를 갖춘 풀 리퀘스트로 정리합니다.

• 데이터베이스가 원인으로 의심되는 지연 조사
• 자주 실행되는 쿼리의 부하 감소
• 수정 전후 속도와 결과 비교

Paperclip에서 단일 Terminal-Bench 과제를 횟수와 시간 상한 내에서 시험합니다. 중단 원인 진단과 제품 수정 승인을 관리하고 같은 작업 사본에서 재시험합니다.

• 상한을 정해 단일 과제 반복 검증
• 벤치마크 중단 원인 진단
• 제품 수정 전 승인 관리

Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.

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

• Investigate an issue from a Sentry URL or short ID
• Review unresolved issues and muted error reports
• Test noise filters and fixes for product bugs

Complete a Dependabot update across a monorepo by updating matching dependency versions in other packages and regenerating bun.lock. Check the changed files, preserve existing version prefixes, then commit and push the fixes.

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

• Completing a partial Dependabot dependency update
• Updating the same dependency across multiple packages
• Regenerating bun.lock after a version update

Reviews Cherry Studio code and documentation against product decisions, architecture rules, implementation checks, and conventions. It selects a review approach based on scope and available agents, then reports findings with guidance for fixes.

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

• Reviewing local changes or a branch
• Checking a pull request before merging
• Reviewing architecture documents and project skills

Investigate a GitHub issue or reported problem, check whether it is a bug, and test a proof of concept. Explain the behavior changes and supporting evidence so the user can decide whether to proceed with the full fix.

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

• Checking whether a reported issue is a real bug
• Testing a proposed fix before full implementation
• Comparing performance before and after a change

Take a pull request through repeated code review and fixes, verify that automated checks pass for the latest commit, and combine its changes into one commit when merging. Conflicts with the request’s goal require confirmation.

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

• Reviewing, fixing, and merging a pull request
• Resolving every review finding, including minor issues
• Checking CI results for the commit being merged

Compare accessibility findings between two versions of a web page. Identify newly introduced and fixed issues, count existing findings, and report evidence and suggested fixes without editing application code.

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

• Check accessibility before committing local changes
• Compare a page against a branch baseline
• Confirm which accessibility issues a change fixed

Implement PR review actions already selected for fixes, run relevant checks, and create focused commits. Post progress and completion replies, resolve applicable threads, and update the action records and their Markdown summary.

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

• Implement review actions already approved for fixing
• Limit review fixes to selected action IDs or files
• Post completion replies and resolve review threads

Work through GitHub pull request feedback by classifying findings, fixing code, running repository checks, and posting replies. With suitable permissions, the skill repeats Copilot reviews until the latest code is reviewed and every thread has an agent response.

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

• Address outstanding Copilot review comments
• Run repeated reviews on a completed pull request
• Explain declined suggestions and hand off design decisions

Monitor selected GitHub Actions checks on an SGLang pull request until they pass on its latest commit. Diagnose failures, push small validated fixes, and retry only failed jobs within defined limits.

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

• Monitor selected PR checks until they pass
• Separate code failures from infrastructure problems
• Apply small fixes and track the resulting checks