agentleFS
PrefectHQPrefectHQ/fastmcp/.agents/skills/fix-issue/SKILL.md

fix-issue

Skill28k starsChanged 27 days agoApache-2.0View on GitHub

Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use python-tests. Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix.

    line 16
  2. Distinctive:

    Run the repository's required dependency sync, full tests, and static checks before committing.

    line 20
  3. Distinctive:

    Start review-pr monitoring after publication.

    line 30

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fix a selected issue

Read AGENTS.md and the contribution policy in the development guide. Read the issue's full discussion, relevant history, and associated PRs in all states. Evaluate existing contributions before writing a competing fix; use review-issue when assignment is the next decision. Preserve contributor authorship when carrying existing work forward.

Establish the contract

Trace the public request to the failing operation. Confirm supported behavior is broken, not merely surprising. State the scope and compatibility boundary before implementation: which inputs must change, which adjacent behavior must remain, and any migration needed. If the intended contract is unresolved, bring that precise question to the maintainer.

Red, green, review

Use python-tests. Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix. Test explicit overrides and neighboring supported paths that share the changed branch. Avoid expanding the fix to unrelated standards gaps.

Self-review the full change with review-pr, including docs and dependency bounds. Separate necessary compatibility changes from accidental regressions and say whether a breaking change remains. Do not infer compatibility from passing tests.

Run the repository's required dependency sync, full tests, and static checks before committing. Honor branch and attribution conventions. If a required check fails, investigate and report evidence rather than hiding the failure.

Publish and follow through

Within existing authorization, update the existing PR or open a focused one, using draft status when appropriate. Follow repository PR-body conventions and the user's pr-body skill when available. Describe the actual user-visible change and any migration, not the development diary.

For a maintainer implementation of a community issue, apply Contributor credit before committing and publishing. Read the issue author's GitHub profile to establish their account identity; prefer the GitHub-provided noreply address, and ask if identity is unclear. Add their Co-authored-by: Name <email> trailer to the implementation commit and at the end of the PR description, alongside existing contributor attribution. Reporting the problem is enough; do not require code or root-cause analysis. Honor opt-outs and do not credit bot accounts as human issue contributors.

Maintainers are generally exempt from supplemental credit checks. For maintainer reports and routine backports, preserve existing community attribution and proceed; do not add a maintainer merely because they opened the original PR or ask for guidance on that basis. A backport does not need a fresh credit audit.

Start review-pr monitoring after publication. CI completion and review completion are distinct. Resolve real findings and report material compatibility decisions; a green check does not settle them. Do not merge or mark ready without authorization.

Download now (ZIP)

Trending

Steady talk.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 7 mentionsApr 2026: 19 mentionsMay 2026: 10 mentionsJun 2026: 6 mentionsJul 2026: 12 mentionsAug 2026: 0 mentionsSep 2026: 11 mentionsOct 2026: 7 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the PrefectHQ/fastmcp repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about PrefectHQ/fastmcp

The biggest 5 of 76 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 76

Talked about on GitHub, YouTube, the web, Hacker News and Bluesky (76 times).

On GitHub · 50

45 more on GitHub

On YouTube · 21

16 more on YouTube

On the web · 3

On Hacker News · 1

On Bluesky · 1

  • Other versions52 projects use a version of this.

    Word for word · 1

    1. jlowin/fastmcp★ 28k100% same

    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. NVIDIA-NeMo/Speech★ 19ksame name
    6. NVIDIA-NeMo/NeMo★ 19ksame name
    7. getsentry/sentry-javascript★ 8.8ksame name
    8. datlechin/TablePro★ 6.3ksame name
    9. TableProApp/TablePro★ 6.3ksame name
    10. docker/docs★ 4.7ksame 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, write-tests 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

    • SentrySkill

      write-tests

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

      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

    • AWSSkill

      ship

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

      Also in 6 projects that use this

    • Microsoft AzureSkill

      build

      Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

      Also in 4 projects that use this

  • In this repository12 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.