beads-issue-tracking

Automate beads (bd) issue tracking and end-of-session git push workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ldsgroups225/Yeko --skill beads-issue-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-issue-tracking
Source: https://github.com/ldsgroups225/Yeko/tree/main/.github/skills/beads-issue-tracking
Command: npx skills add https://github.com/ldsgroups225/Yeko --skill beads-issue-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads issue tracking and the end-of-session push workflow are critical for maintaining visibility and ensuring clean handoffs in complex software projects. This skill provides a structured approach to starting work on an issue, updating progress, and syncing changes.

Core Features & Use Cases

  • Unified issue queue and status tracking for beads (bd) tasks.
  • Enforced rules for session end: status updates, notes, blockers, and push to remote.
  • Guidance for aligning with repository workflows and code review cycles.

Quick Start

Select an issue, set its status to in_progress, and begin recording notes as you work.

Frequently Asked Questions about beads-issue-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track issue status and sync updates with git pushes at the end of a session?

To track issue status and sync updates with git pushes, this workflow enforces structured status changes, notes, and blockers before allowing a mandatory remote push at session close. It automates the synchronization to ensure clean handoffs.

What is the best way to manage a beads issue queue during active software development?

Managing a beads issue queue requires setting task statuses to in_progress and recording real-time progress notes. This workflow provides a unified queue and status tracking system to maintain visibility across development teams.

Can I enforce code review cycles and pull request alignment using a structured git workflow?

You can enforce code review cycles and pull request alignment through this structured workflow. It provides guidance for aligning repository workflows with mandatory status updates before syncing changes to the remote repository.

How do I record blockers and notes for in-progress code issues before pushing to remote?

Recording blockers and notes for code issues before pushing to remote is handled by enforced session-end rules. The workflow mandates logging status updates and blockers to maintain project visibility before completing a git push.

Does this issue tracking workflow require any specific dependencies or environment setup?

This issue tracking workflow requires no specific dependencies or environment setup to function. It operates directly within your existing software project environment to automate beads task queues and git synchronization.

When should I use an automated issue tracking workflow for git repository synchronization?

You should use an automated issue tracking workflow for git repository synchronization when handling complex software projects that require strict status reviews and clean handoffs across development teams.