agentleFS
crazynomadcrazynomad/notebooklm-jetpack/skills/fix-issue/SKILL.md

fix-issue

Skill133 starsChanged 8 months agoNo licenceView on GitHub

Drive a single GitHub issue through a full confirm → reproduce → diagnose → fix → verify → report lifecycle, posting progress back to the issue and escalating if it can't be fixed. Use this whenever the user wants to work a specific numbered issue in this repo — e.g. "/fix-issue 57", "fix issue #42", "解决 issue 57", "看一下 #88 这个 bug", "帮我修 #103 并在 issue 上汇报". Trigger even when the user only gives an issue number and a verb like "fix"/"修"/ "solve"/"处理", and even when they don't spell out the whole SOP — running the full SOP is the point of this skill.

  • Commits and pushes

We split this skill into the rules it gives an agent

17 rules. 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

  • Other versions51 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 51

    1. pytorch/pytorch★ 105ksame name
    2. ZhuLinsen/daily_stock_analysis★ 67ksame name
    3. Dokploy/dokploy★ 38ksame name
    4. remix-run/remix★ 33ksame name
    5. jlowin/fastmcp★ 28ksame name
    6. PrefectHQ/fastmcp★ 28ksame name
    7. NVIDIA-NeMo/Speech★ 19ksame name
    8. NVIDIA-NeMo/NeMo★ 19ksame name
    9. getsentry/sentry-javascript★ 8.8ksame name
    10. datlechin/TablePro★ 6.4ksame name

    41 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use document, prepare-release and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • nicolasestremSkill

      document

      Create focused documentation for specific components or features

      Also in 4 projects that use this

    • ShopifySkill

      prepare-release

      Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install

      Also in 3 projects that use this

    • GitHubSkill

      refactor

      Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

      Also in 5 projects that use this

    • SentrySkill

      write-tests

      Write tests following project conventions. Use when adding new tests or modifying existing ones.

      Also in 3 projects that use this

    • AWSSkill

      ship

      Finalize dev work on an issue branch — update docs, push, and open a PR.

      Also in 6 projects that use this

    • MicrosoftSkill

      adversarial-review

      Adversarial review of a system design from 6 critical perspectives -- SRE, security, staff engineer, finance, operator, and developer advocate. Produces a unified risk assessment. Use for INTERACTIVE on-demand reviews during a design conversation (/adversarial-review). For RECIPE-DRIVEN reviews (where prior step context is needed), use the systems-design-critic agent instead.

      Also in 3 projects that use this

  • In this repository2 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.