DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to build and test AI-DLC harness packages from source with Aidlc Workflows

Use the repo's Bun scripts to regenerate harness packages from core, check that output is deterministic, and run smoke, unit and integration tests before a change.

Short answer: Clone the repo and run bun install --frozen-lockfile; then make your change in core/ or harness/ only, never in the generated dist output, since that is overwritten; generate packages with bun scripts/package.ts. All steps.

Who it is forA contributor or platform engineer customising AI-DLC stages, agents or rules for their company.

The problemHand editing generated files breaks on the next release, and changes to one harness can silently drift from the others.

The outcomePackages rebuilt from core, a determinism check that fails on drift, and test results you can attach to a pull request.

What you need first

  • macOS, Linux, WSL or Windows PowerShell
  • A supported coding agent

Steps

  1. Clone the repo and run bun install --frozen-lockfile
  2. Make your change in core/ or harness/ only, never in the generated dist output, since that is overwritten
  3. Generate packages with bun scripts/package.ts
  4. Run the determinism guard: bun scripts/package.ts --check
  5. Run tests: bun tests/run-tests.ts --ci
  6. Before a release run bun tests/run-tests.ts --release

Prompt for your agent

In my clone of awslabs/aidlc-workflows, change <stage or rule> in core/, regenerate packages, run the determinism check and the CI tests, and summarise any failures with the file that caused each.

Caveat. Building from source needs Bun, unlike the native install.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for awslabs/aidlc-workflows and "Build and test AI-DLC harness packages from source"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer