resolve-refs

Extract cross-references from documents and code into follow-up plans.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill resolve-refs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-refs
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/resolve-refs
Command: npx skills add https://github.com/AGM1968/weave --skill resolve-refs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams identify and follow cross-references embedded in tasks, code, and documents so related work stays connected and nothing falls through the cracks.

Core Features & Use Cases

  • Reference extraction: Detects identifiers like wv-xxxxxx, gh issues, ADR/RFCs, and file paths, compiling a follow-up plan.
  • Guided follow-up: Provides recommended commands to review and gather full context for each reference.
  • Guardrails: Enforces a maximum of 10 references per pass, prevents automatic fetching, and blocks recursion to keep workflows safe and predictable.

Quick Start

Scan the current task context to surface actionable follow-up commands.

Frequently Asked Questions about resolve-refs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify and extract cross-references from code and documentation?▼

To identify and extract cross-references, this skill scans tasks, codebases, and documents to detect identifiers like issue links and file paths, compiling a structured follow-up plan for related work.

What is the best way to follow references across tasks without missing related files?▼

Following references across tasks requires systematic detection of node IDs and file paths. This skill maps related issues and documents, providing recommended commands to gather full context safely.

How do I extract issue numbers and file paths from task descriptions in bulk?▼

Extracting issue numbers and file paths from task descriptions is done by scanning the context for embedded identifiers. It enforces a maximum of 10 references per pass to ensure workflows remain predictable.

Does this reference extraction tool automatically fetch linked files and issues?▼

No, this reference extraction tool does not automatically fetch linked files. It provides guided follow-up commands for manual review and strictly blocks recursive invocations to maintain safe operations.

What are the limitations when resolving references across a codebase?▼

Limitations when resolving references include a maximum of 10 references per pass, no automatic fetching of external links, and no recursive invocations, keeping the follow-up workflow safe and predictable.

Can I use this to map ADRs and RFCs mentioned in task tracking documents?▼

Yes, you can use this to map ADRs, RFCs, and similar identifiers mentioned in task tracking documents. It detects these cross-references and generates a plan to review the full context of each linked item.