Results for “bisect”

Instrument code to support efficient git bisect by producing deterministic pass/fail signals and concise runtime summaries for each tested commit. Use when debugging regressions with git bisect, automating bisect workflows, creating bisect test scripts, handling flaky tests during bisection, or needing clear exit codes and logging for automated bisect runs. Helps identify the exact commit that introduced a bug through automated testing.

The English summary is being prepared. Showing the original description.

Manage complex Git histories with guidance for reorganizing commits, copying selected changes between branches, and finding bug-introducing commits. It also covers working on multiple branches at once and recovering lost commits through Git's reference history.

• Clean up commit history before opening a pull request
• Apply selected commits to another branch
• Find the commit that introduced a bug

Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.

• Committing related changes in focused groups
• Reorganizing branch history with rebase or squash
• Tracing when and where code changed

Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and confidence levels.

The English summary is being prepared. Showing the original description.

Investigate failing tests, broken builds, and unexpected behavior through a structured debugging process. Reproduce the failure, narrow down its source, fix the root cause, and add a regression test that catches the same problem.

• Investigating a test that fails after a code change
• Finding the cause of a broken build
• Tracing a feature that stopped working

Organize code changes into focused commits that follow the project's existing message style. Clean up branch history with rebase, resolve conflicts, and investigate when particular code changed or who last modified a line.

• Splitting changes into focused commits
• Matching the project's commit message style
• Cleaning up branch history before merging

Investigate recurring SGLang automated test failures by comparing logs, commit history, and GPU environments. Narrow down code changes or machine-specific problems, optionally reproduce failures remotely, and summarize the evidence in a structured report.

• Finding the change behind a recurring test failure
• Checking whether failures depend on a GPU or runner
• Reproducing a test failure on a remote GPU server

Investigate errors, crashes, and unexpected behavior by reproducing failures, tracing execution, and comparing logs. Tests one explanation at a time, then provides a verified fix, supporting evidence, and tests or safeguards to prevent recurrence.

• Investigate error messages and execution traces
• Find the cause of an application crash
• Compare logs to locate a failure

Investigate bugs and failing tests through four stages: finding the root cause, comparing working patterns, testing a hypothesis, and implementing a fix. Uses reproduction steps, diagnostic evidence, and regression tests to check the result.

• Tracing the cause of a failing test
• Following runtime errors back to invalid data
• Finding the change that broke working code

Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component, function, or line is faulty. Covers binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions across TypeScript, SQL, and bash.

The English summary is being prepared. Showing the original description.

Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them — that is ai-bug-triage. Generating tests from specs rather than from a defect — that is ai-test-generation. Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.

The English summary is being prepared. Showing the original description.

Expert in navigating and manipulating git history. Covers finding bugs with bisect, understanding code evolution, recovering lost work, and rewriting history safely. Understands that git history is your time machine. Use when "git history, git bisect, find when bug introduced, recover deleted, rewrite history, git blame, lost commit, " mentioned.

The English summary is being prepared. Showing the original description.

Perform a ruler-and-compass construction with step-by-step justification for each operation, producing a constructible geometric figure from given elements. Covers classical Euclidean constructions including perpendicular bisectors, angle bisectors, parallel lines, regular polygons, and tangent lines. Use when given geometric elements (points, segments, angles) and asked to produce a Euclidean construction, verify constructibility, or generate ordered construction steps for educational or documentation purposes.

The English summary is being prepared. Showing the original description.

Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).

The English summary is being prepared. Showing the original description.

rebase、cherry-pick、bisect、worktree、reflogを含む高度なGitワークフローをマスターし、クリーンな履歴を維持し、あらゆる状況から回復。複雑なGit履歴の管理、フィーチャーブランチでの協働、リポジトリ問題のトラブルシューティング時に使用。

The English summary is being prepared. Showing the original description.

Handles git work: atomic commits, rebase, squash, blame, bisect, reflog, and history questions. Use whenever a task needs a commit or a git-history investigation; skip for ordinary code edits.

The English summary is being prepared. Showing the original description.

Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.

The English summary is being prepared. Showing the original description.

[omh] Git branch in trouble -- a merge conflict, a commit that broke something, history to repair: plan the resolution, the bisect, or the rewrite, name what is already pushed first, and force-push only with `--force-with-lease`. Use when the user says: git-workflow, git workflow, merge conflict, merge conflicts, rebase conflict, resolve the conflict, resolve this conflict, conflict markers.

The English summary is being prepared. Showing the original description.

Advanced git workflows including worktrees, bisect, interactive rebase, hooks, and recovery techniques

The English summary is being prepared. Showing the original description.

Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.

The English summary is being prepared. Showing the original description.

Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.

The English summary is being prepared. Showing the original description.

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

The English summary is being prepared. Showing the original description.

Fully automated ship workflow: pre-flight, merge base, run tests, coverage audit, pre-landing review, design review, adversarial review, version bump, CHANGELOG generation, TODOS.md update, bisectable commits, push and PR creation, auto-sync docs via document-release.

The English summary is being prepared. Showing the original description.