Agent Skills › withkynam/vibecode-pro-max-kit › vc-generate-context

vc-generate-context

GitHub

维护项目权威上下文文件all-context.md，支持缺失时全量扫描或存在时增量更新。通过检测仓库状态生成路由协议及分组文档，确保跨代理知识同步与准确性。

.claude/skills/vc-generate-context/SKILL.md withkynam/vibecode-pro-max-kit

Trigger Scenarios

仓库上下文缺失、过时或与代码矛盾时需要刷新特定包、功能或架构区域的上下文时

Install

npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -g -y

More Options

Non-standard path

npx skills add https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context -g -y

Use without installing

npx skills use withkynam/vibecode-pro-max-kit@vc-generate-context

指定 Agent (Claude Code)

npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a claude-code -g -y

安装 repo 全部 skill

npx skills add withkynam/vibecode-pro-max-kit --all -g -y

预览 repo 内 skill

npx skills add withkynam/vibecode-pro-max-kit --list

SKILL.md

Frontmatter

{
    "name": "vc-generate-context",
    "layer": "contract",
    "metadata": {
        "author": "vibecode-pro-max-kit",
        "version": "1.0.0"
    },
    "description": "Generate or update the project's authoritative repository context at process\/context\/all-context.md. Use when repo context is missing, stale, or contradicted by code.",
    "trigger_keywords": "generate context, update context, refresh context, missing context"
}

Generate Context

Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Use this skill to maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.

Optional input: a package, app, feature, context group, or architectural area to refresh first.

Workflow

Read references/generate-context.md for the full context contract.
Determine mode:
- Full scan when process/context/all-context.md is missing.
- Delta update when it exists.
Read process/context/all-context.md when present to identify relevant grouped context files.
Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant process/context/**/*.md docs.
Produce process/context/all-context.md PLUS process/context/{group}/all-{group}.md for each detected or approved group (see Invocation Modes below).
Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.

Validate the generated context:

node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs

If routing or grouped context changed, also run:

node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs

Rules

Treat process/context/ as durable cross-agent knowledge.
Treat process/context/all-context.md as the durable routing protocol; do not replace it with generated prose.
Do not store agent-specific mechanics here unless they affect project workflow.
Do not rewrite grouped context docs; if they are stale or mis-grouped, flag audit-context.
Prefer concise, factual, path-specific documentation.
Use pnpm terminology for package management.
Treat validation failures as blockers before presenting context as refreshed.

Invocation Modes

Mode	Trigger	Group-detection	Output
`setup-delegation`	Called by vc-setup passing an approved-groups list	Skip re-detection; use the list provided	`all-context.md` + `all-{group}.md` for each approved group
`standalone-full`	Direct invocation with no groups list	Self-detect groups via the detection table in `references/generate-context.md`	`all-context.md` + `all-{group}.md` for all detected groups
`delta`	Invoked when context already exists; update context	Self-detect; create MISSING groups only; warn on unrecognized; never delete	`all-context.md` updated + any new `all-{group}.md` files created