agentleFS
juicedatajuicedata/juicefs/.agents/skills/issue/SKILL.md

issue

Skill15k starsChanged 3 days agoApache-2.0View on GitHub

Analyze issues, bug reports, and feature requests. Clarify the problem, check the evidence, and give a concise conclusion and next step.

53 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 5 mentionsFeb 2026: 1 mentionMar 2026: 3 mentionsApr 2026: 0 mentionsMay 2026: 3 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 4 mentionsSep 2026: 6 mentionsOct 2026: 8 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the juicedata/juicefs repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about juicedata/juicefs

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

See all 77

Talked about on GitHub, YouTube, Hacker News and Bluesky (77 times).

On GitHub · 39

34 more on GitHub

On YouTube · 25

20 more on YouTube

Used with

Projects with it also use branch, commit and 9 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.
  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 19 projects that use this

  • vertz-devSkill

    backlog

    Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking

    Also in 3 projects that use this

  • CodeWithBehnamSkill

    browse

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 7 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 4 projects that use this

  • +1 more from Azure
  • Other versions53 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 53

    1. remotion-dev/remotion★ 73ksame name
    2. tldraw/tldraw★ 51ksame name
    3. tokio-rs/toasty★ 3.3ksame name
    4. dataplat/dbatools★ 2.9ksame name
    5. pch/rawmakase★ 1.6ksame name
    6. aws/graph-explorer★ 492same name
    7. egregore-labs/egregore★ 293same name
    8. finos/git-proxy★ 263same name
    9. alamenai/terrae★ 245same name
    10. awslabs/loom★ 202same name

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

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Follow trusted AGENTS.md and contribution guidelines.

    line 8
  2. Distinctive:

    Default to analysis only. Do not modify files, post comments, or change GitHub state unless the user requests it.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 51 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

Analysis

  • Follow trusted AGENTS.md and contribution guidelines. Read the issue and relevant discussion; check the reported behavior against the affected version, code, documentation, and related issues or PRs.
  • Separate the reported symptom, verified behavior, and suspected cause. An unverified root cause or missing reproduction does not disprove the problem. Ask only for missing information that changes the conclusion or next action.
  • For feature requests, establish the actual use case and why existing behavior is insufficient before discussing implementation. Identify duplicates or existing fixes only when supported by evidence.

Output

Respond in Chinese, translating the labels below and using this order. Keep each item brief, with short sentences and clear actors. Skip introductions, investigation diaries, and repeated context.

  • Problem: Explain the reported problem, when it occurs, and its impact in one or two short sentences. For requests, state the use case and current limitation.
  • Assessment: Say whether this is a defect, expected behavior, or needs more evidence or discussion. Qualify uncertainty and give a root cause only when supported.
  • Evidence: Link only decisive evidence next to the claim it supports. State verification scope once; distinguish author reports, code-based conclusions, and independent reproduction.
  • Next step: Give one concrete action, with the most important check or missing fact when needed.

Default to analysis only. Do not modify files, post comments, or change GitHub state unless the user requests it.

Download now (ZIP)

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.