skills.rest
AutumnsGrove
AutumnsGroveCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vulture-sweep

Automate issue board cleanup by verifying code completion and consolidating fragmented tasks.

5|Updated Nov 22, 2025
Search Tags:#automation#github#cleanup#issues#triage#backlog management
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill vulture-sweep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vulture-sweep
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/vulture-sweep
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill vulture-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious process of cleaning up and organizing issue boards by identifying and resolving stale, implemented but unclosed, or fragmented issues.

Core Features & Use Cases

  • Issue Hygiene: Regularly cleans up accumulated cruft on issue boards.
  • Identification: Spots issues that are implemented but not closed, stale/outdated, or fragmented.
  • Verification: Verifies issue completion directly in the codebase before closing.
  • Consolidation: Merges fragmented issues into single, actionable tasks.
  • Use Case: After a major release, use this Skill to automatically close all issues that were implemented during the release but never marked as done, ensuring your backlog accurately reflects completed work.

Quick Start

Run the vulture-sweep skill to clean up the issue board.

Frequently Asked Questions about vulture-sweep

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

FAQPage Schema
How do I automate GitHub issue triage and close implemented issues?▼

Automate GitHub issue triage by scanning your codebase to identify open issues that have already been implemented, verifying completion, and automatically closing them to maintain an accurate backlog.

What is the best way to clean up a stale GitHub issue backlog?▼

The best way to clean up a stale GitHub issue backlog is to run an automated sweep that identifies outdated or fragmented issues, verifies their status in the codebase, and consolidates or resolves them.

How does issue verification in the codebase work before closing backlog items?▼

Issue verification works by cross-referencing open backlog items against the actual codebase to confirm whether the requested features or fixes have truly been implemented before automatically closing the tickets.

Can I consolidate fragmented GitHub issues into single actionable tasks?▼

Yes, you can consolidate fragmented GitHub issues by running an automated backlog sweep that identifies overlapping or duplicated tasks and merges them into single, actionable issues for better project tracking.

When should I run an issue board cleanup after a major release?▼

You should run an issue board cleanup after a major release to automatically close all issues that were implemented during the release cycle but never marked as done, ensuring your backlog accurately reflects completed work.

Related Skills

Explore More Software Engineering Skills→
zerwizzerwiz

github-auth

Configure GitHub authentication for repository, pull request, issue, and CI access.

Community
Advanced
salmanrranasalmanrrana
7

brain-dump-tickets

Create, update, and track Brain Dump tickets and epics across projects.

Community
Intermediate
rjroyrjroy
6

add-item

Create GitHub issues and link them to a configured GitHub Project.

Community
Intermediate
amadeus-dlcamadeus-dlc
5

gh-issue-organizer

Classify, group, and prioritize open GitHub issues for backlog triage.

Official
Advanced