dev.kit

Simple session flow for developers and agents.

npm install -g @udx/dev-kit
dev.kit → dev.kit repo → dev.kit agent

Enriched context from repository signals.Experienced workflows from GitHub history.

No npm? curl -fsSL https://dev.kit.sh | bash

Step 1

Run the flow

Start with the CLI. Each command moves the session forward and tells the next actor what to do.

dev.kit

Start here

Detect the repo, check the environment, and get the exact next command.

$ dev.kit

[required]
  ✓ git — version control, branch analysis
  ✓ gh — GitHub repo experience
  ✓ npm — package installs

> udx.dev • runtime-image • profile node

[do next]
  run: dev.kit repo
dev.kit repo

Generate repo context

Build .rabbit/context.yaml from repo definitions, source files, and GitHub signals.

$ dev.kit repo

> udx.dev • runtime-image • mode: learn

[read first]
  - ./README.md
  - ./docs

[factors]
  documentation ✓ present
  dependencies ✓ present
  config ◦ partial
  pipeline ✓ present

[gaps]
  - 1 factor(s) missing or partial

[context]
  - .rabbit/context.yaml

[next]
  run: dev.kit agent
dev.kit agent

Generate agent workflow

Turn repo context into AGENTS.md, with instructions and templates shaped by best practices plus GitHub repo experience. That includes telling the agent to start each new session with the same three commands.

$ dev.kit agent

> udx.dev • runtime-image • profile node

[commands]
  verify make test
  build make build

[context]
  AGENTS.md generated workflow and instructions for agents
  .rabbit/context.yaml generated repo context from source and GitHub signals

[ready]
  - Context synced. Start your session following AGENTS.md workflow.
  - Start each new session with dev.kit → dev.kit repo → dev.kit agent to resync.
Step 2

Generated Context And Workflow

Once the three commands run at session start, the agent is instructed to begin future sessions the same way so it re-acknowledges current repo context and workflow before doing work.

.rabbit/context.yaml

Generated Repo Map

Commands, refs, dependencies, GitHub context, and gaps, generated from the repo itself. That includes the workflows, Docker images, actions, and config references that shape how the repo builds and deploys.

# Real example: andypotanin/udx.dev
repo:
  name: udx.dev
  archetype: runtime-image
  profile: node

commands:
  verify: make test
  build:  make build

refs:
  - ./README.md
  - ./docs
  - ./.github/workflows
  - ./src

github:
  repo: andypotanin/udx.dev
  open_issues: 10
  recent_prs: 5

dependencies:
  - base image: udx-worker/udx-worker:latest
  - action: actions/checkout

gaps:
  - config (partial)
AGENTS.md

Agent contract

AGENTS.md tells agents how to start, what to read, how to verify work, and how to follow GitHub workflow in this repo. It also makes the session-start flow repeatable so the agent keeps reloading current context instead of relying on stale memory.

  • Start each repo session with dev.kit → dev.kit repo → dev.kit agent
  • Read repo manifests and refs before scanning code
  • Use linked GitHub issues and PR templates
  • Verify locally before reporting done
  • Refresh context after repo changes
# AGENTS.md — auto-generated by dev.kit agent
# Source of truth: .rabbit/context.yaml

## Rules  (8 contract rules)
## Workflow  (repo → agent → work → PR → merge)
  - Refresh repo context with dev.kit → dev.kit repo → dev.kit agent
  - Read linked GitHub issue and confirm scope
  - Inspect git status

## Templates  (PR, issue, close-out)
## Practices  (best practices + repo experience)
Copied