Skills MCP Plugins Subagents

Browse by category

Coding Skills2061 Marketing Skills1580 Design Skills1479 Security Skills1134 Automation Skills994 Testing Skills985 Media Skills908 Infrastructure Skills902 Data Skills883 Finance Skills840 Automation MCPs799 Planning Skills797 DevTool MCPs797 Documentation Skills757 Coding MCPs738 Productivity Skills721 Productivity MCPs649 Data MCPs505 DevTool Skills503 Infrastructure MCPs482 Security MCPs441 Debugging Skills428 Code review Skills415 Search & RAG MCPs409

The Monday digest

The week's best new agents, skills and MCP servers. One email, every Monday.

Free · unsubscribe anytime.

aaaa.fyi

Every agent skill, MCP server, plugin and subagent — searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

Agent Skills MCP Servers Plugins Subagents Coding Agents

Collections Official publishers Glossary Blog Search Saved Feedback

Privacy Terms llms.txt Sitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/loopkit/bisect-regression

home/skills/archive228/loopkit/bisect-regression

bisect-regression

712stars129forks

How to install bisect-regression?

archive228/loopkit/bisect-regression

$npx -y skills add Archive228/loopkit --skill bisect-regression

Installs into the current project.

Summary

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

Files · 1

SKILL.md

1	# Bisect the Regression
2	1. Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
3	2. `git bisect start; git bisect bad <bad>; git bisect good <good>`.
4	3. At each step, run the SMALLEST test that distinguishes good from bad. Mark `git bisect good/bad`.
5	4. When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
6	5. `git bisect reset`. Report: the commit, the line, the one-sentence cause.
7	Automate it: `git bisect run ./repro.sh` if you have a script that exits non-zero on the bug.

Archive228Publisher · 56 listings

Preview

Archive228/loopkit

# Bisect the Regression

1. Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.

2. `git bisect start; git bisect bad <bad>; git bisect good <good>`.

3. At each step, run the SMALLEST test that distinguishes good from bad. Mark `git bisect good/bad`.

$ npx -y skills add Archive228/loopkit --skill bisect-regression

▸ installing to .claude/skills…

✓ bisect-regression ready

RepoArchive228/loopkit

LicenseMIT

CategoryDebugging

UpdatedJul 2026

Repo stars712

First seenJul 22, 2026

Tags

People who liked this also viewed

6 picks

Type

azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026472k1.3k
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026197k259k
safe-debugRigor 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 SkillsMay 2026161k507
explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026161k507
minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026161k507
insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 202618k31