You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Elijah Voigt 283712770f feat(nbd): implement partial ID matching [c9d551] Add `resolve_id` to `store.rs` that resolves a full ticket ID from an exact match or a unique prefix (like git short-SHA resolution). Use it in `cmd_read`, `cmd_update`, and `validate_deps` so all three accept short prefixes. Ambiguous prefixes produce an error listing all matches. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		3 months ago
..
.claude	Scaffolding for nbd cli	3 months ago
.nbd/tickets	feat(nbd): implement nbd migrate command [0f51af]	3 months ago
docs	docs(nbd): add README, PLANNING, ARCHITECTURE, and complete Phase 6	3 months ago
src	feat(nbd): implement partial ID matching [c9d551]	3 months ago
tests	feat(nbd): implement partial ID matching [c9d551]	3 months ago
CLAUDE.md	Scaffolding for nbd cli	3 months ago
Cargo.lock	feat(nbd): scaffold crate with module stubs and dependencies	3 months ago
Cargo.toml	feat(nbd): scaffold crate with module stubs and dependencies	3 months ago
PLAN.md	docs(nbd): add README, PLANNING, ARCHITECTURE, and complete Phase 6	3 months ago
README.md	feat(nbd): implement nbd migrate command [0f51af]	3 months ago

README.md

Unescape Escape

nbd

A CLI tool for managing work tickets, primarily targeted at agent workflows.

Tickets are stored as JSON files in .nbd/tickets/ inside the nearest ancestor directory that contains a .nbd/ folder, discovered by traversing upward from the current working directory — just like git finds .git/.

How it works

Each ticket is a JSON file named {id}.json, where id is a unique 6-character lowercase hex string (e.g. a3f9c2). Tickets carry:

Field	Type	Default
`id`	6-char hex string	auto-generated
`title`	string	(required)
`body`	string	`""`
`priority`	integer 0–10	`5`
`status`	`todo` \| `in_progress` \| `done`	`todo`
`ticket_type`	`project` \| `feature` \| `task` \| `bug`	`task`
`dependencies`	list of ticket IDs	`[]`

All commands accept --json for machine-readable output.

Usage

Initialise

Create the tickets directory manually in your project root:

mkdir -p .nbd/tickets

Create a ticket

nbd create --title "Fix login bug" --priority 8 --type bug
nbd create --title "Add rate limiting" --body "Protect public endpoints" --deps a3f9c2

Read a ticket

nbd read a3f9c2
nbd read a3f9c2 --json

List all tickets

nbd list
nbd list --json

Update a ticket

Only the flags you supply are changed; all other fields retain their current values.

nbd update a3f9c2 --status in_progress
nbd update a3f9c2 --priority 9 --type bug

Migrate ticket files

Re-serialise all ticket files through the current schema. Use this after upgrading nbd to remove stale fields, add new fields with defaults, and normalise formatting.

nbd migrate
nbd migrate --dry-run   # preview changes without writing
nbd migrate --json      # machine-readable summary

Running

# From the nbd/ directory
cargo run -- create --title "Test ticket" --priority 7 --type bug
cargo run -- list
cargo run -- read <id>
cargo run -- update <id> --status in_progress
cargo run -- list --json

Testing

cargo test

Unit tests live in src/tests.rs. Integration tests (full command flows against a temporary directory) live in tests/integration.rs.

Development

Run these commands in order before committing:

cargo fmt
cargo check
cargo clippy
cargo test

License

Dual-licensed under Apache License, Version 2.0 and MIT License, consistent with the rest of the vibed mono-repo.

This software was written with Claude Code using the claude-sonnet-4-6 model.

README.md Unescape Escape

nbd