agentleFS
Sign inStart free
medusajsmedusajs/medusa/.claude/skills/triaging-issues/SKILL.md

triaging-issues

Skill37k starsChanged 10 months agoLicence not identifiedView on GitHub

Triages GitHub issues for the Medusa repository. Use when a GitHub issue is opened or receives a new comment. Categorizes and validates the issue, then emits a structured triage decision (one outcome: fix, escalate, feature, needs-info, rewrite, slop, close, or none, plus template, labels, and an optional Linear ticket) for a downstream deterministic step to apply. Accepts issue number as required argument plus optional title, body, and author.

We split this skill into the rules it gives an agent

16 rules. 0 are common, 9 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

The licence could not be identified — 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 5 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.

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about medusajs/medusa

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

See all 67

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

On GitHub · 33

28 more on GitHub

On Bluesky · 15

10 more on Bluesky

On YouTube · 9

4 more on YouTube

On the web · 3

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. pytorch/pytorch★ 105ksame name
    2. vercel-labs/eve-software-factory-template★ 1.2ksame name
    3. microsoft-foundry/foundry-agent-webapp★ 124same name
    4. vercel-labs/kody-eve-template★ 13same name
    5. getsentry/software-factory★ 0same name

    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 github-linear-bridging and writing-quality.

    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.
    • SentrySkill

      github-linear-bridging

      Conventions for bridging GitHub and Linear: creating Linear issues from GitHub issues, cross-referencing the two trackers, and checking whether a GitHub issue is already tracked in Linear. Load when asked to create Linear issues from GitHub issues, link the trackers in either direction, or report tracking status. Not needed for work that stays inside one tracker.

      Also in 3 projects that use this

    • SentrySkill

      writing-quality

      Writing-quality guardrails for any prose the agent drafts or edits: pull request descriptions, issue comments, review reports, Linear replies. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or tool plumbing.

      Also in 3 projects that use this

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

Reviews can't be read right now.

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.

Check your setup, free