chunk-update-references

Validate and update code references in chunk GOAL.md files.

3|1|Updated Jan 8, 2026

Search Tags:#documentation #static-analysis #chunk #code-references #backreference

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-update-references

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chunk-update-references
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/chunk-update-references
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill chunk-update-references

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the code references in a chunk's GOAL.md are accurate, up-to-date, and point to existing symbols across the repository, preventing drift between documentation and implementation.

Core Features & Use Cases

Reference discovery: identifies all current code references used by a chunk's goal and checks their validity.
Bidirectional linking: ensures chunk files reference code correctly and code symbols have backreferences to the chunk.
Remediation guidance: suggests updated symbol paths or file locations when refactors occur, and flags ambiguities for human review.

Quick Start

Run the updater to refresh and validate the chunk-goal code references.

Frequently Asked Questions about chunk-update-references

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

FAQPage Schema

How do I keep documentation references aligned with code after refactoring?▼

To keep documentation references aligned with code after refactoring, validate the code references in each chunk's GOAL.md to ensure they point to existing symbols. If references have moved or been renamed, update them and verify bidirectional backreferences.

What is bidirectional backreference validation for code documentation?▼

Bidirectional backreference validation for code documentation ensures that chunk files reference code symbols correctly and that those code symbols also contain backreferences pointing back to the chunk, preventing drift between implementation and goals.

How do I update code references in GOAL.md files when symbols are renamed?▼

To update code references in GOAL.md files when symbols are renamed, run the updater to discover all current references, check their validity, and apply suggested updated symbol paths or file locations to remediate the drift.

What happens when static analysis detects ambiguous code references in documentation?▼

When static analysis detects ambiguous code references in documentation, it flags those ambiguities for human review and prompts for HISTORICAL status if the references are obsolete, producing a concise change summary of the findings.

Do I need any external dependencies to validate chunk code references?▼

No external dependencies are required to validate chunk code references. The Skill operates independently to identify, validate, and update code references in each chunk's GOAL.md without relying on external packages.