Agent skill

Break Loop

by jlifeng in jlifeng/JobPilot

“Break the Loop - Deep Bug Analysis”

— description from SKILL.md by jlifeng
Apache-2.0Auto-check passedTesting & QA

Install Break Loop

skills CLI
$ npx skills add jlifeng/JobPilot --skill break-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jlifeng/JobPilot break-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jlifeng/JobPilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/break-loop .claude/skills/break-loop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
break-loop
GitHub stars
140
Token cost
~1.1k tokens
SKILL.md length
472 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

  • Works in 5 steps: Root Cause Category → Why Fixes Failed (if applicable) → Prevention Mechanisms → …
  • SKILL.md covers Analysis Framework, Output Format, Core Philosophy and After Analysis: Immediate…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

About this skill

Break Loop is a skill in jlifeng/JobPilot (140 stars). Its SKILL.md is about 1.1k tokens. Licence: Apache-2.0.

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Root Cause Category
  2. Why Fixes Failed (if applicable)
  3. Prevention Mechanisms
  4. Systematic Expansion
  5. Knowledge Capture

What it can do on your machine

Read from SKILL.md and the folder at commit 7f33542. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Break Loop loads about 1.1k tokens when it runs. Until then it costs about 11 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~11
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jlifeng/JobPilot at commit 7f33542, republished under its Apache-2.0 licence (© jlifeng). 472 words, ~1,131 tokens.

Download SKILL.mdSave it as .claude/skills/break-loop/SKILL.md (or your agent's skills folder).
name
break-loop
description
Break the Loop - Deep Bug Analysis

Break the Loop - Deep Bug Analysis

When debug is complete, use this skill for deep analysis to break the "fix bug -> forget -> repeat" cycle.


Analysis Framework

Analyze the bug you just fixed from these 5 dimensions:

1. Root Cause Category

Which category does this bug belong to?

CategoryCharacteristicsExample
A. Missing SpecNo documentation on how to do itNew feature without checklist
B. Cross-Layer ContractInterface between layers unclearAPI returns different format than expected
C. Change Propagation FailureChanged one place, missed othersChanged function signature, missed call sites
D. Test Coverage GapUnit test passes, integration failsWorks alone, breaks when combined
E. Implicit AssumptionCode relies on undocumented assumptionTimestamp seconds vs milliseconds
2. Why Fixes Failed (if applicable)

If you tried multiple fixes before succeeding, analyze each failure:

  • Surface Fix: Fixed symptom, not root cause
  • Incomplete Scope: Found root cause, didn't cover all cases
  • Tool Limitation: grep missed it, type check wasn't strict
  • Mental Model: Kept looking in same layer, didn't think cross-layer
3. Prevention Mechanisms

What mechanisms would prevent this from happening again?

TypeDescriptionExample
DocumentationWrite it down so people knowUpdate thinking guide
ArchitectureMake the error impossible structurallyType-safe wrappers
Compile-timeTypeScript strict, no anySignature change causes compile error
RuntimeMonitoring, alerts, scansDetect orphan entities
Test CoverageE2E tests, integration testsVerify full flow
Code ReviewChecklist, PR template"Did you check X?"
4. Systematic Expansion

What broader problems does this bug reveal?

  • Similar Issues: Where else might this problem exist?
  • Design Flaw: Is there a fundamental architecture issue?
  • Process Flaw: Is there a development process improvement?
  • Knowledge Gap: Is the team missing some understanding?
Show full SKILL.md (194 more words)Show less
5. Knowledge Capture

Solidify insights into the system:

  • Update .trellis/spec/guides/ thinking guides
  • Update .trellis/spec/backend/ or frontend/ docs
  • Create issue record (if applicable)
  • Create feature ticket for root fix
  • Update check skills if needed

Output Format

Please output analysis in this format:

markdown
## Bug Analysis: [Short Description]

### 1. Root Cause Category
- **Category**: [A/B/C/D/E] - [Category Name]
- **Specific Cause**: [Detailed description]

### 2. Why Fixes Failed (if applicable)
1. [First attempt]: [Why it failed]
2. [Second attempt]: [Why it failed]
...

### 3. Prevention Mechanisms
| Priority | Mechanism | Specific Action | Status |
|----------|-----------|-----------------|--------|
| P0 | ... | ... | TODO/DONE |

### 4. Systematic Expansion
- **Similar Issues**: [List places with similar problems]
- **Design Improvement**: [Architecture-level suggestions]
- **Process Improvement**: [Development process suggestions]

### 5. Knowledge Capture
- [ ] [Documents to update / tickets to create]

Core Philosophy

The value of debugging is not in fixing the bug, but in making this class of bugs never happen again.

Three levels of insight:

  1. Tactical: How to fix THIS bug
  2. Strategic: How to prevent THIS CLASS of bugs
  3. Philosophical: How to expand thinking patterns

30 minutes of analysis saves 30 hours of future debugging.


After Analysis: Immediate Actions

IMPORTANT: After completing the analysis above, you MUST immediately:

  1. Update spec/guides - Don't just list TODOs, actually update the relevant files:

    • If it's a cross-platform issue → update cross-platform-thinking-guide.md
    • If it's a cross-layer issue → update cross-layer-thinking-guide.md
    • If it's a code reuse issue → update code-reuse-thinking-guide.md
    • If it's domain-specific → update backend/*.md or frontend/*.md
  2. Sync templates - After updating .trellis/spec/, sync to src/templates/markdown/spec/

  3. Commit the spec updates - This is the primary output, not just the analysis text

The analysis is worthless if it stays in chat. The value is in the updated specs.

© jlifeng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/break-loop of jlifeng/JobPilot.

Open the folder on GitHubat commit 7f33542

Compare with similar skills

Break Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Break Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Break Loop this skilljlifeng/JobPilot140—~1.1kAutomated safety check: PassApache-2.0
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Clawteam DevHKUDS/ClawTeam5.5k1 repos~1.1kAutomated safety check: PassMIT
Browser Testing with Chrome DevToolsaddyosmani/agent-skills103k4 repos~3.5kAutomated safety check: WarnMIT
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Clawteam Dev

    HKUDS/ClawTeam

    A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…

    5.5k GitHub starsUsed in 1 repo~1.1k tokens
    Testing & QAAuto-check passed
  • Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.

    103k GitHub starsUsed in 4 repos~3.5k tokens
    Testing & QAAuto-check: warnings
  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed
  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from jlifeng/JobPilot

  • Brainstorm

    jlifeng/JobPilot

    Brainstorm - Requirements Discovery (AI Coding Enhanced). An agent skill from jlifeng/JobPilot.

    140 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Update Spec

    jlifeng/JobPilot

    Update Code-Spec - Capture Executable Contracts. An agent skill from jlifeng/JobPilot.

    140 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Finish Work

    jlifeng/JobPilot

    Finish Work - Pre-Commit Checklist

    140 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Start

    jlifeng/JobPilot

    Start Session

    140 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Questions about Break Loop

How do I install Break Loop in Claude Code?

Run `npx skills add jlifeng/JobPilot --skill break-loop -a claude-code`. Or copy the skill folder (.agents/skills/break-loop in jlifeng/JobPilot) into .claude/skills/break-loop in your project. Claude Code loads it when a task matches its description.

How do I install Break Loop in Codex?

Run `npx skills add jlifeng/JobPilot --skill break-loop -a codex`. Or copy the skill folder (.agents/skills/break-loop in jlifeng/JobPilot) into .agents/skills/break-loop in your project. Codex loads it when a task matches its description.

Can I use Break Loop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jlifeng/JobPilot --skill break-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/break-loop, .gemini/skills/break-loop, .github/skills/break-loop and .opencode/skills/break-loop in your project.

What does Break Loop need to run?

SKILL.md names no scripts, command-line tools or credentials: Break Loop is instructions for the agent only.

Does Break Loop access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Break Loop safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Break Loop use?

Break Loop is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Break Loop use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Break Loop?

Skills that share tags, products or a category with Break Loop: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars), Clawteam Dev (HKUDS/ClawTeam, 5.5k stars) and Browser Testing with Chrome DevTools (addyosmani/agent-skills, 103k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Break Loop?

jlifeng (a GitHub user) maintains it in jlifeng/JobPilot, which has 140 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: jlifeng/JobPilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.