repo-packet-builder

Generate deterministic repository review packets with scope and evidence artifacts.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-packet-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-packet-builder
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/repo-packet-builder
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-packet-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill enables deterministic construction of scoped repository review packets for CodeBuddy-style specialist lanes, reducing ambiguity and manual packet assembly.

Core Features & Use Cases

  • Builds a bounded, scope-defined packet that explicitly states target scope, included and excluded surfaces, and high-signal evidence references.
  • Generates key artifacts (run_manifest.json, repo_scope.md, repo_inventory.json, evidence_index.json) and assignment maps for downstream lanes.
  • Supports whole-repo, path-scoped, and diff-context reviews to streamline code reviews and compliance workflows.

Quick Start

Provide the repository root and an optional output path to generate a CodeBuddy repo packet ready for downstream specialization.

Frequently Asked Questions about repo-packet-builder

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

FAQPage Schema
How do I assemble a repository review packet for automated code reviews?

To assemble a repository review packet, provide the repository root and an optional output path to generate scoped artifacts like run_manifest.json, repo_scope.md, and repo_inventory.json for downstream specialist lanes.

Can I scope code reviews to a specific path or diff instead of the whole repository?

Yes, you can scope code reviews to specific paths or diff contexts. The packet builder supports whole-repo, path-scoped, and diff-context reviews to streamline targeted code analysis and compliance workflows.

What artifacts are generated when constructing a scoped repository review packet?

Constructing a scoped repository review packet generates key artifacts including run_manifest.json, repo_scope.md, repo_inventory.json, and evidence_index.json to define target scope, exclusions, and evidence references.

Does the repository packet builder modify or mutate the source repository?

No, the repository packet builder does not mutate the source repository. It assembles deterministic review packets by enumerating scope, assets, and evidence references while avoiding any mutation of the original codebase.

What's the best way to reduce ambiguity when assigning code review tasks to specialist lanes?

To reduce ambiguity in specialist lane assignments, use a deterministic packet builder that explicitly states target scope, included and excluded surfaces, and high-signal evidence references for bounded assignments.

Do I need to manually specify exclusions when generating a repository inventory?

No, you do not need to manually specify all exclusions. The packet construction process applies explicit target scope and bounded specialist assignments to automatically generate a deterministic repository inventory.