133 lines
4.0 KiB
Markdown
133 lines
4.0 KiB
Markdown
# Skills-Vault Request: Review Context Builder
|
|
|
|
Date: 2026-06-19
|
|
|
|
Requested supplier repository:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\skills-vault
|
|
```
|
|
|
|
Requesting CCPE artifacts:
|
|
|
|
```text
|
|
agents/agent-specs/ccra-local-reviewer.agent.md
|
|
runtimes/hybrid/ccra-local-review.runtime.md
|
|
```
|
|
|
|
## 1. Capability Name
|
|
|
|
```text
|
|
review-context-builder
|
|
```
|
|
|
|
## 2. Product / Runtime Context
|
|
|
|
Local CCRA review needs a repeatable way to assemble review context from project files, review bundles, reports, diffs, validation outputs, and prior decisions before invoking the reviewer Agent.
|
|
|
|
The first consumer is The Mindscape of Bro Tsong, but the operation should remain a generic context-pack builder for file-first review, handoff, and agent-invocation workflows.
|
|
|
|
## 3. Repeated Action Or Friction Point
|
|
|
|
Humans and runtime operators spend too much time moving files and explaining review context to Agents or external reviewers. A reusable context builder should reduce transfer work by generating a compact context index and file manifest from local evidence.
|
|
|
|
This should not be a CCRA-only tool. It should support any workflow where an Agent needs a file-first context package before review, audit, planning, synthesis, or handoff.
|
|
|
|
## 4. Inputs
|
|
|
|
Expected input:
|
|
|
|
```text
|
|
project_root: path
|
|
review_id: string
|
|
context_profile: optional profile name
|
|
source_roots: list of files or directories
|
|
output_dir: path
|
|
include_patterns: list
|
|
exclude_patterns: list
|
|
metadata: optional key/value map
|
|
```
|
|
|
|
The `metadata` field may include project-specific values such as `round_id`, `review_goal`, `non_goals`, or `target_reviewer`, but these must not be hard-coded into the Skill.
|
|
|
|
## 5. Expected Outputs
|
|
|
|
Write:
|
|
|
|
```text
|
|
review-context.md
|
|
review-file-manifest.json
|
|
```
|
|
|
|
The context should include:
|
|
|
|
```text
|
|
review_id
|
|
context_profile
|
|
source_roots
|
|
files_included
|
|
files_excluded
|
|
important_reports
|
|
test_or_validation_outputs
|
|
diff_or_changed_file_references
|
|
prior_decision_references
|
|
known_non_goals
|
|
open_questions_for_reviewer_or_agent
|
|
machine_readable_manifest
|
|
```
|
|
|
|
## 6. Allowed Actions
|
|
|
|
- Read configured files and directories.
|
|
- Generate a context index, not a judgment report.
|
|
- Write outputs only to the caller-specified `output_dir`.
|
|
|
|
## 7. Forbidden Actions
|
|
|
|
- Do not summarize source evidence in a way that replaces file reading.
|
|
- Do not make CCRA findings.
|
|
- Do not edit project files.
|
|
- Do not create review bundles.
|
|
- Do not decide review acceptance, round closure, lifecycle status, release readiness, or task approval.
|
|
|
|
## 8. Validation Expectation
|
|
|
|
The Skill should include tests for:
|
|
|
|
```text
|
|
complete context build
|
|
missing source root
|
|
excluded large files
|
|
manifest path normalization
|
|
UTF-8 paths and Chinese filenames
|
|
stable output ordering
|
|
metadata passthrough without hard-coded CCRA fields
|
|
```
|
|
|
|
## 9. Reusability Rationale
|
|
|
|
The context builder is deterministic file orchestration. It can serve Local CCRA review, article review, code review, release review, model-card review, Skill release review, and manual Web upload preparation. The review judgment belongs in the calling Agent or human reviewer; context-pack assembly belongs in `skills-vault` once the file contract stabilizes.
|
|
|
|
Example non-CCRA consumers:
|
|
|
|
```text
|
|
writing-workbench:
|
|
build article review context from source notes, outline, prior reviewer reports, and decision logs.
|
|
|
|
video-workbench:
|
|
build script / storyboard / asset review context before a production review.
|
|
|
|
skills-vault:
|
|
build release review context from Skill source, tests, fixtures, README, and install notes.
|
|
|
|
ccpe-system:
|
|
build Agent or Runtime review context from specs, templates, validation notes, and prior decisions.
|
|
|
|
development repositories:
|
|
build PR / release review context from diffs, test logs, issue references, and deployment notes.
|
|
```
|
|
|
|
## 10. Current Blocked Task
|
|
|
|
The first Local CCRA Runtime can create context manually, but repeated use should call this Skill to reduce transfer friction and improve review consistency. Other review and handoff workflows can use the same Skill without depending on Local CCRA.
|