mcpField
J
jb-beans

jb-beans

github.com/bjesuiterDevelopment036 installsUpdated 1w ago
Repository

About jb-beans

jb-beans is a skill for using the Beans Go CLI to manage Git-friendly Markdown issues in a repository. It guides agents through repository-specific workflows, structured issue relationships, and cautious updates.

Key features

  1. 01Read repository guidance with beans prime
  2. 02List and inspect issues as JSON
  3. 03Create and update issues
  4. 04Track parent and blocking relationships
  5. 05Guard concurrent edits with --if-match
  6. 06Check configuration and relationships

Use cases

  1. 01Find ready-to-work issues in a repository
  2. 02Record implementation progress and decisions
  3. 03Represent dependencies between issues
  4. 04Avoid overwriting concurrent issue edits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bjesuiter/skills --skill jb-beans

After installing, type/jb-beansin Claude Code to confirm it loaded.

Bundled filesbeans-prime.ts

Details

From the project README

Beans

Use beans to manage Git-friendly Markdown issues stored in .beans/.

Start with project guidance

Before working in a Beans-enabled repository, run:

beans prime

Follow its output. It defines the repository's workflow, issue model, statuses, and agent expectations and takes precedence over generic guidance here.

Installation and binary safety

Install the Go CLI through Homebrew or Go:

brew install hmans/beans/beans
# or
go install github.com/hmans/beans@latest

Never install beans with npm or Bun. The package with that name is an unrelated legacy Node program. If Beans fails unexpectedly, especially with a coffee-script module error, diagnose command shadowing:

which -a beans
beans version

Use an absolute path to the working Homebrew or Go binary when necessary, then leave broader PATH repair outside the task.

Agent workflow

Prefer --json whenever a command supports it. A typical lifecycle is:

# Discover actionable or existing work
beans list --json --ready
beans list --json -S "login"
beans show --json <id>

# Create and start work
beans create --json "Add login screen" -t feature -s todo -d "Build the initial login UI"
beans update --json <id> -s in-progress

# Record useful progress
beans update --json <id> --body-append "## Notes\n\nStarted implementation"

# Complete with a durable summary
beans update --json <id> -s completed \
  --body-append "## Summary of Changes\n\nImplemented and validated the feature."

Keep issue bodies current with reproduction details, decisions, checklists, progress, and final summaries. Use structured parent/blocking relationships instead of duplicating dependencies only in prose.

Use narrow body replacements or --if-match updates when concurrent edits could otherwise overwrite content. Run beans check after substantial configuration or relationship changes. Archive work only when the project workflow or user requests it.

Discover current commands

Do not rely on a copied command catalog. Inspect the installed CLI because supported fields and flags can change:

beans --help
beans <command> --help
beans version

For advanced filtering and relationship traversal, inspect beans graphql --help and beans graphql --schema. Beans has no built-in beans tui; use the separate beans-tui tool when requested.

Project: https://github.com/hmans/beans

Comments

Markdown supported