'bug-fixing' 검색 결과

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.

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

Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.

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

• Reproducing and fixing reported SDK bugs
• Investigating failing tests
• Fixing regressions in automated CI checks

Prepare a bug-fixing run by recovering reproduction details and tests, checking the workspace, and finding existing fixes. Select the appropriate workflow for a reproduction session, CI run, bug ticket, or requested PR changes.

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

• Recover reproduction tests from a session or CI run
• Check the workspace before starting a bug fix
• Find existing fixes before choosing an approach

Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.

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

Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.

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

Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with thorough investigation and regression testing.

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

Standard Operating Procedures for backend development, bug fixing, DevOps, infrastructure deployment, and security hardening.

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