dev-grooming

Groom stale DEV-labeled issues in the beeminder/blog repository.

3|3|Updated May 3, 2022
One-click install
npx skills add https://github.com/beeminder/blog --skill dev-grooming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-grooming
Source: https://github.com/beeminder/blog/tree/main/.claude/skills/dev-grooming
Command: npx skills add https://github.com/beeminder/blog --skill dev-grooming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

Groom DEV-labeled issues in the beeminder/blog project by surfacing the most stale issues, evaluating them for clarity, actionability, and labeling correctness, and guiding preferred improvements before moving to the next item.

Core Features & Use Cases

  • Surface the least-recently-updated DEV issues (excluding ZzZ and snoozed) and present full details for quick assessment.
  • Analyze issues for clarity, acceptance criteria, scope and actionability; suggest improvements including label updates, description edits, splitting work, snoozing, or marking resolved.
  • Execute user-approved actions via a dedicated grooming session helper, then continue with the next stale issue automatically.

Quick Start

Start a grooming session by running the developer grooming workflow for the beeminder/blog repo and following the on-screen prompts to review and act on the top stale DEV issue.

Frequently Asked Questions about dev-grooming

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

FAQPage Schema
How do I automatically groom and triage stale GitHub issues in my backlog?

To groom stale GitHub issues automatically, this Skill surfaces the least-recently-updated DEV issues, evaluates them for clarity and actionability, and suggests label updates or snoozing before executing your approved actions.

What is the best way to review and update issue labels for old development tasks?

Reviewing and updating issue labels for old tasks is handled by evaluating each surfaced issue's scope and suggesting corrections like label updates, description edits, or splitting work before applying the changes via the GitHub CLI.

Do I need the GitHub CLI to manage and snooze development issues?

Yes, you need the GitHub CLI and jq installed to manage and snooze development issues, as the Skill relies on these dependencies to fetch, review, and modify issues directly within the repository.

Can I exclude snoozed or inactive issues from my backlog grooming workflow?

You can exclude inactive issues from backlog grooming because the Skill automatically filters out ZzZ and snoozed items, ensuring it only surfaces the oldest open DEV issues that require immediate attention.

How does issue triage handle splitting large development tasks into smaller ones?

Issue triage handles large tasks by analyzing each issue's scope and actionability, then suggesting improvements like splitting the work into smaller items or applying resolution labels, which are executed only after you approve the action.