Results for “issue-tracking”

Creates a GitHub issue from a specification file using a feature request template, checking for existing issues first.

Manages issues and dependencies through the Beads CLI, covering creation, updates, queries, and closure.

Publishes a reviewed GitHub issue draft by creating or editing an issue with the gh CLI, assigning it to the current user, and never commenting, closing, or reopening issues.

Progress Tracking

Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.

Clusters a GitHub issue backlog by root cause into plan-master issues, redirects children with a standardized comment, and bundles architectural-fix PRs that close clusters atomically.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

동시에 굴리던 여러 워크트리를 한 번에 통합합니다. 각 워크트리와 연결된 이슈를 확인하고 증거로 실제 해결 여부를 판정한 뒤, merge 를 시도하기 전에 충돌을 확정하고 계획한 순서대로 누적 검증해 순서 때문에 깨지는 경우까지 잡아냅니다. 충돌은 작업 브랜치 쪽에서 양쪽 의도를 보존하는 방향으로 해소해 승인받고, 비판 서브에이전트로 모호성을 걸러낸 다음 PR 을 merge 하고 통합 테스트로 재검증하고 이슈를 닫습니다. `$issue-merge`, "워크트리 전부 merge", "이슈들 통합", "PR 충돌 해결하고 합쳐줘" 요청과 issue-end 에서 merge 를 선택했을 때 사용합니다.

Create, list, and view GitHub issues using the gh CLI with guided workflows for gathering titles, descriptions, labels, and reproduction steps.

issue-create, issue-start, issue-end, issue-merge에서 이슈 진행 상태가 성공적으로 전환된 직후 issue-onboard 그래프 캐시를 동기화합니다. `$issue-graph-sync

Systematically trace bugs backward through call stack to find original trigger

Create, search, triage, and label GitHub issues using the gh CLI or REST API, with guidance on avoiding duplicates and managing the backlog.

Safely reuse, create, update, or explicitly close the single GitHub Issue that tracks repository work

Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

User Request

Project Tracking — Structured Active Project Files

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

Move issues and external pull requests through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

issue-start 가 증거와 리포트를 게시하고 사람이 승인한 작업을 마무리합니다. 기존 증거의 완결성과 게시 상태를 확인하고, 부족하거나 바뀐 경우에만 보강·재게시한 뒤 PR 을 만듭니다. merge 는 하지 않고 issue-merge 로 넘깁니다. `$issue-end`, "이슈 마무리", "작업 종료", "승인한 작업 PR" 요청에 사용합니다.

Load this skill when the user says "tech debt", "tech-debt", or "/tech-debt", or asks to file/track something they've identified as tech debt. Verifies the claimed problem still exists in the current code, drafts a single [Tech Debt]-prefixed issue from `.github/ISSUE_TEMPLATE/tech-debt-issue.md`, and creates it via `gh issue create` only after the user approves the draft.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

GitHub 이슈를 완전 스냅샷으로 다시 읽어 `.issue/graph.json` 캐시를 생성·갱신합니다. "$issue-sync", "이슈 그래프 갱신", "그래프 만들기", issue-onboard가 그래프 없이 시작될 때 사용합니다.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

GitHub Sync

Implements error tracking and crash reporting in Flutter apps using Sentry and Firebase Crashlytics, including automatic error capture, enriched context, breadcrumbs, and CI/CD integration for source maps and debug symbols.

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Follow a request end-to-end through the stack from route to database

Issue Fleet