metagit-upstream-scan
Skill4 starsChanged 12 days agoMITView on GitHub
Use when a coding agent encounters likely upstream blockers and must find related workspace repositories, files, and probable root causes.
In this repository62 other files it gives its agents.
- agentsAGENTS.md
- docs/agents.mdAGENTS.md
- agentsAGENTS.md
- agentsCopilot instructions
- .cursor/rules/github-cli.mdcCursor rule
- .cursor/rules/project-level.mdcCursor rule
- llms.txtllms.txt
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-guideSkill
- gitnexus-impact-analysisSkill
- gitnexus-refactoringSkill
- humanizerSkill
- metagit-agent-accessSkill
- metagit-agent-coordinationSkill
- metagit-aosSkill
- metagit-bootstrapSkill
- metagit-campaignSkill
- metagit-cliSkill
- metagit-config-refreshSkill
- metagit-context-packSkill
- metagit-control-centerSkill
- metagit-gatingSkill
- metagit-gitnexusSkill
- metagit-graph-maintainSkill
- metagit-mcp-resourcesSkill
- metagit-multi-repoSkill
- metagit-projectsSkill
- metagit-release-auditSkill
- metagit-repo-impactSkill
- metagit-rewrite-campaignSkill
- metagit-sharing-stateSkill
- metagit-stampSkill
- metagit-upstream-scanSkill
- metagit-upstream-triageSkill
- metagit-workspace-scopeSkill
- metagit-workspace-syncSkill
- metagit-agent-accessSkill
- metagit-agent-coordinationSkill
- metagit-aosSkill
- metagit-bootstrapSkill
- metagit-campaignSkill
- metagit-cliSkill
- metagit-cliSkill
- metagit-config-refreshSkill
- metagit-context-packSkill
- metagit-control-centerSkill
- metagit-gatingSkill
- metagit-gitnexusSkill
- metagit-graph-maintainSkill
- metagit-mcp-resourcesSkill
- metagit-multi-repoSkill
- metagit-projectsSkill
- metagit-release-auditSkill
- metagit-repo-impactSkill
- metagit-rewrite-campaignSkill
- metagit-sharing-stateSkill
- metagit-stampSkill
- metagit-upstream-triageSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the current repo does not appear to contain the full fix and related repositories may hold the source issue.
- Distinctive: line 19
Use this token-efficient wrapper for upstream discovery tasks:
- Very specific: line 29
Read workspace repository map from active .metagit.yml.
- Very specific: line 30
Run metagit_workspace_index to verify repo availability and sync state.
- Very specific: line 31
Use metagit_workspace_search with category preset (terraform, docker, infra, ci).
- Very specific: line 32
Use metagit_upstream_hints to rank candidate repositories and files.
- Distinctive: line 40
Start narrow with issue-specific terms (error, module, variable, image tag).
- Distinctive: line 42
Prefer repositories referenced by workspace metadata before searching unknown repos.
- Distinctive: line 55
Keep this workflow read-only unless an explicit sync action is requested.
≈ “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.
Files
Metagit Upstream Discovery Skill
Use this skill when the current repo does not appear to contain the full fix and related repositories may hold the source issue.
Supported Use Cases
- Missing Terraform input in a shared module
- Docker base image/version mismatch across repos
- Shared infrastructure definitions causing local failures
- CI pipeline breakages tied to upstream templates/workflows
Local Script Wrapper (Use First)
Use this token-efficient wrapper for upstream discovery tasks:
./scripts/upstream-scan.sh [root_path] "<query>" [preset] [max_results]
Output format:
- compact status line
- top ranked repo hints (
hint) - top search file hits (
hit)
Workflow
- Read workspace repository map from active
.metagit.yml. - Run
metagit_workspace_indexto verify repo availability and sync state. - Use
metagit_workspace_searchwith category preset (terraform,docker,infra,ci). - Use
metagit_upstream_hintsto rank candidate repositories and files. - Return a concise action plan:
- top candidate repos
- likely files/definitions
- whether sync is needed before deeper analysis
Search Strategy
- Start narrow with issue-specific terms (error, module, variable, image tag).
- Expand to broader shared terms if no hits.
- Prefer repositories referenced by workspace metadata before searching unknown repos.
Output Contract
Return:
- ranked candidates with rationale
- suggested next file openings
- confidence level and unresolved assumptions
Safety Rules
- Restrict search to configured workspace repositories.
- Cap result size and duration.
- Keep this workflow read-only unless an explicit sync action is requested.
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
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.

