agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-upstream-triage/SKILL.md

metagit-upstream-triage

Skill4 starsChanged 13 days agoMITView on GitHub

Triage cross-repository blockers by ranking likely upstream repositories and files with metagit search and hinting tools. Use when local fixes appear incomplete.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill for failures likely rooted in another repository.

    line 8
  2. Distinctive:

    Run workspace index and search with issue-specific terms.

    line 12
  3. Distinctive:

    Run upstream hint ranking to prioritize repositories/files.

    line 13
  4. Distinctive:

    Keep this flow read-only unless sync is explicitly requested.

    line 30

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

Triaging Upstream Blockers

Use this skill for failures likely rooted in another repository.

Workflow

  1. Run workspace index and search with issue-specific terms.
  2. Run upstream hint ranking to prioritize repositories/files.
  3. Open the top candidates and validate root-cause evidence.
  4. Return a short fix path (repo, file, next action).

Command Wrapper

  • ./skills/metagit-upstream-scan/scripts/upstream-scan.sh [root_path] "<query>" [preset] [max_results]

Output Contract

Return:

  • ranked candidate repositories
  • probable root-cause files
  • confidence and assumptions

Safety

  • Keep this flow read-only unless sync is explicitly requested.

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