agentleFS
Sign inStart free
VercelKnown publishervercel-labs/xref/skills/issue-graph/SKILL.md

issue-graph

Skill163 starsChanged 6 days agoApache-2.0View on GitHub

Read-only context for issues, pull requests, and backlogs. Use to trace related work, check PR counts, prioritize follow-ups, filter saved captures, open exact dashboard views, replay triage queries, or compare snapshots.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. vercel-labs/issue-graph★ 163100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Before running operational commands, load and read the guidance bundled with the CLI:

    line 8
  2. Distinctive:

    Follow the returned core guidance.

    line 14
  3. Distinctive:

    If the executable, skills command, core, or referenced assets are unavailable, stop and report the CLI/skill mismatch and the observed …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

issue-graph

Before running operational commands, load and read the guidance bundled with the CLI:

issue-graph skills get core

Follow the returned core guidance. When detailed workflows or references are needed, load and read them through the CLI:

issue-graph skills get core --full

Discover available guidance with issue-graph skills list. Inspect command syntax with issue-graph skills --help, issue-graph skills list --help, or issue-graph skills get --help.

If the executable, skills command, core, or referenced assets are unavailable, stop and report the CLI/skill mismatch and the observed error. Do not fabricate operational guidance, fall back to remembered instructions, or automatically install or upgrade anything. Ask for an explicitly authorized setup correction before proceeding.

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.

Check your setup, free