vc-generate-context

Generate and update the authoritative repository context file at process/context/all-context.md.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-generate-context-hyusecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc-generate-context
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-generate-context
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-generate-context-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Repository documentation drifts out of sync with the actual codebase, leaving AI agents and developers without a reliable source of truth about project structure, stack, and conventions. This Skill scans the repo and produces a maintained, validated context layer. ## Core Features & Use Cases - Full and Delta Modes: Performs a full scan when context is missing, or a delta update that preserves stable sections and records changes since the last update. - Context Group Detection: Detects domains like database, auth, CI/CD, and infra from project signals and generates per-group context files under process/context/. - Built-in Validation: Ships a Node.js validator that checks required sections, freshness dates, secret leakage, and broken path references before context is accepted. - Use Case: After adding a new database layer and CI pipeline to a monorepo, run this Skill to refresh all-context.md, create the new database/ and cicd/ group docs, and validate the result. ## Quick Start Ask the AI to generate or refresh the repository context at process/context/all-context.md using the vc-generate-context skill.

Frequently Asked Questions about vc-generate-context

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

FAQPage Schema
How do I generate repository context documentation automatically?▼

Invoke the skill to scan the codebase and write process/context/all-context.md plus per-group files like process/context/database/all-database.md. It records the scan timestamp, repo HEAD, changes, open questions, and source references.

How do I update stale project context without rewriting everything?▼

Use delta mode, which runs when all-context.md already exists. It preserves unchanged sections, adds a changes-since-last-update section, creates only missing group files, and never deletes existing ones.

What context groups does the detection table support?▼

The detection table covers database, container, auth, cicd, infra, uxui, and workflows groups, triggered by signals like Prisma, Dockerfiles, CI configs, or Terraform. A group is created only when at least two dedicated source files exist for that domain.

Does the context validator catch secrets in documentation?▼

Yes. The validate-all-context.mjs script fails the run if it detects secret-like patterns such as API keys, private keys, or database URLs with credentials. It also warns on stale dates, missing sections, and broken path references.

When should I run a full scan versus a delta update?▼

Run a full scan when process/context/all-context.md does not exist, such as during initial project setup. Use delta mode whenever the file exists and you only need to bring drifted sections up to date.