rocq-bisect
>
Tech stack
Works with
--- name: rocq-bisect description: > license: Apache-2.0 --- # Bisecting Rocq Regressions Use this skill when you already have a reproducible regression and need to find the release or commit that changed behavior. Keep `SKILL.md` for the tiered decision process; use the guide for exact commands and reporting detail. ## Instructions - Minimise the failing example first; do not bisect a noisy or flaky test. - Choose the cheapest tier that can answer the question: release, Docker, then source. - Make the pass/fail command deterministic before running any bisect loop. - Confirm one known-good and one known-bad endpoint before narrowing the range. - Record exact versions, tags, or commits as you go. - Re-run the final culprit manually before reporting it. ## Workflow Checklist 1. Produce a standalone test file or script, ideally with `rocq-mwe`. 2. Decide whether release bisection, Docker bisection, or `git bisect` is appropriate. 3. Validate the good and bad endpoints on the same test. 4. Automate the pass/fail condition with a shell command or script. 5. Run the bisect loop and save the first bad release or commit. 6. Package the result with the minimized example and environment summary. ## Notes - Use `rocq-setup` when you need help managing opam switches during release bisection. - The full tier-by-tier procedures, anti-patterns, and reporting checklist live in [references/guide.md](references/guide.md). ## References - [guide.md](references/guide.md)
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
