ワンクリックでManusで任意のスキルを実行

managing-beads

スター43

フォーク5

更新日2026年4月28日 11:26

Project issue tracker using bd (Beads). Issues travel via git through .beads/issues.jsonl. Use when asked to work on, pick, or fix an issue; when capturing discovered work; or when checking what to do next.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

andrzejchm

andrzejchm/fdb

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Managing Beads Issues

Session workflow

Run bd prime — loads context and shows open/claimed issues.
Pick work with bd ready, claim with bd update <id> --claim.
Work on code. Create follow-up issues as you discover them.
Commit issues.jsonl together with the code it tracks (the pre-commit hook exports it automatically).
Before context compaction: run bd sync to flush any pending writes.
Close finished issues with bd close <id>.

Core commands

bd prime                                                          # Session start: load context
bd ready                                                          # List unclaimed available issues
bd show <id>                                                      # View issue details
bd update <id> --claim                                            # Claim an issue
bd update <id> --status=in-progress                               # Update status
bd create --title="..." --description="..." --type=task --priority=2  # Create an issue
bd close <id>                                                     # Mark issue done
bd sync                                                           # Flush pending writes (before compaction)
bd bootstrap                                                      # Rebuild local DB after git pull
bd github sync                                                    # Bidirectional sync with GitHub Issues
bd github sync --pull-only                                        # Pull from GitHub only
bd github sync --push-only                                        # Push to GitHub only

Creating issues

bd create \
  --title="Add scroll support for web" \
  --description="CDP-based scroll not yet implemented; fdb scroll fails on web targets." \
  --type=task \
  --priority=2

Types: task, bug, feature, chore
Priorities: 1 (critical) → 4 (low)

Rules

On main: git add .beads/issues.jsonl && git commit directly — the pre-commit hook exports to the right place.
Always commit issues.jsonl together with the code changes it tracks — never in isolation.
Run bd bootstrap after git pull on any machine that already has a local DB.
Run bd prime at session start only — not during compaction (bd sync handles compaction).
Never run bd doctor --fix — it can corrupt the local DB.
bd is the source of truth; GitHub Issues are a mirror — sync with bd github sync.
Capture any work discovered during implementation as new issues immediately.

Working in a git worktree

The pre-commit hook always exports to the main repo's .beads/issues.jsonl, not the worktree's copy. The "Exported N issues" message does not mean it was staged in the worktree.

Before committing from a worktree, manually copy and stage:

cp <repo-root>/.beads/issues.jsonl .beads/issues.jsonl
git add .beads/issues.jsonl
git commit -m "chore(bd): sync issues — <summary>"

Never push a worktree branch with a stale issues.jsonl.

このリポジトリの他の Skills

同じリポジトリ

using-fdb

andrzejchm/fdb

Uses fdb (Flutter Debug Bridge) CLI to interact with running Flutter apps on devices and simulators. Launches or attaches to apps, hot reloads, screenshots, reads app logs (`fdb logs`) and native system logs (`fdb syslog` — Android logcat, iOS syslog, macOS log), fetches OS-level crash records (`fdb crash-report` — jetsam, LMK, native .ips), inspects widget trees, describes screens including off-screen GridView/ListView children, taps/inputs/scrolls/swipes/navigates, forces garbage collection (`fdb gc`), and grants/revokes/resets runtime permissions (`fdb grant-permission`). Use when launching or attaching to a Flutter app on device (including apps started outside fdb via Xcode/simctl/adb), hot reloading, taking screenshots, reading app or native system logs, diagnosing native crashes (jetsam, LMK), fetching post-mortem crash reports, inspecting or describing the UI, interacting with widgets via fdb, forcing a GC to disambiguate live-retained vs unreachable-but-uncollected memory, or pre-granting runtime perm

2026-07-1743

testing-fdb

andrzejchm/fdb

Testing and developing fdb (Flutter Debug Bridge). Covers running the smoke test suite, individual command tests, static analysis, and the test app. Use when running fdb tests, adding new commands, verifying fdb behavior, or preparing a release.

implementing-fdb-features

andrzejchm/fdb

Implements features, functionalities, and improvements to fdb and its packages. Use when creating new features, adding new commands, or improving existing functionality in fdb or fdb_helper.

2026-05-1143

releasing-fdb

andrzejchm/fdb

Prepares and publishes new fdb releases. Covers version bumping (fdb + fdb_helper lockstep), pre-release verification (smoke tests, analysis), pub.dev publishing, git tagging, and GitHub release creation. Use when bumping the version, preparing a release, publishing to pub.dev, creating a GitHub release, or tagging a new version.

2026-04-3043

Managing Beads Issues

Session workflow

Run bd prime — loads context and shows open/claimed issues.

Pick work with bd ready, claim with bd update <id> --claim.

Work on code. Create follow-up issues as you discover them.

Commit issues.jsonl together with the code it tracks (the pre-commit hook exports it automatically).

Before context compaction: run bd sync to flush any pending writes.

Close finished issues with bd close <id>.

Core commands

bd prime # Session start: load context bd ready # List unclaimed available issues bd show <id> # View issue details bd update <id> --claim # Claim an issue bd update <id> --status=in-progress # Update status bd create --title="..." --description="..." --type=task --priority=2 # Create an issue bd close <id> # Mark issue done bd sync # Flush pending writes (before compaction) bd bootstrap # Rebuild local DB after git pull bd github sync # Bidirectional sync with GitHub Issues bd github sync --pull-only # Pull from GitHub only bd github sync --push-only # Push to GitHub only

Creating issues

bd create \ --title="Add scroll support for web" \ --description="CDP-based scroll not yet implemented; fdb scroll fails on web targets." \ --type=task \ --priority=2

Types: task, bug, feature, chore
Priorities: 1 (critical) → 4 (low)

Rules

On main: git add .beads/issues.jsonl && git commit directly — the pre-commit hook exports to the right place.

Always commit issues.jsonl together with the code changes it tracks — never in isolation.

Run bd bootstrap after git pull on any machine that already has a local DB.

Run bd prime at session start only — not during compaction (bd sync handles compaction).

Never run bd doctor --fix — it can corrupt the local DB.

bd is the source of truth; GitHub Issues are a mirror — sync with bd github sync.

Capture any work discovered during implementation as new issues immediately.

Working in a git worktree

The pre-commit hook always exports to the main repo's .beads/issues.jsonl, not the worktree's copy. The "Exported N issues" message does not mean it was staged in the worktree.

Before committing from a worktree, manually copy and stage:

cp <repo-root>/.beads/issues.jsonl .beads/issues.jsonl git add .beads/issues.jsonl git commit -m "chore(bd): sync issues — <summary>"

Never push a worktree branch with a stale issues.jsonl.

name	managing-beads
description	Project issue tracker using bd (Beads). Issues travel via git through .beads/issues.jsonl. Use when asked to work on, pick, or fix an issue; when capturing discovered work; or when checking what to do next.