Automate GitHub issue lifecycle from creation to closure with synchronized local files.
npx skills add https://github.com/0xxmemo/litellmctl --skill issue-0xxmemo
Please help me install this Agent Skill. Skill: issue Source: https://github.com/0xxmemo/litellmctl/tree/main/skills/issue Command: npx skills add https://github.com/0xxmemo/litellmctl --skill issue-0xxmemo
This skill automates the GitHub issue lifecycle: file new issues from descriptions, seed ISSUE.md and DISCOVERY.md, and guide the team through create, plan, execute, and close flows with consistent structure across the repository.
Create a new GitHub issue from a description and seed ISSUE.md and DISCOVERY.md for it.
High-intent search queries and answers about installing and using this skill.
Automate GitHub issue lifecycle management by using subcommands to create, edit, plan, execute, and close issues. The workflow seeds local ISSUE.md and DISCOVERY.md files, rewrites planning documents in full to reflect current understanding, and organizes local state within a dedicated issues directory.
Keep DISCOVERY.md and PLAN.md synchronized by rewriting them in full during the plan and edit phases to reflect the current project understanding, rather than appending changelog entries, ensuring discovery and planning documents stay aligned with the remote GitHub issue state.
Automatically close GitHub issues by pushing avenue branches and opening pull requests in dependency order, each containing a Closes #N hook. This ensures the remote GitHub issue auto-closes upon successful pull request merge without manual intervention.
No external dependencies are required to manage local state. The tool operates independently, utilizing a single issues/<number>-<slug>/ directory structure to organize local ISSUE.md files, DISCOVERY.md, and PLAN.md without relying on additional components.
Implement a GitHub issue plan without mutating remote state by using the execute subcommand. This action processes the local PLAN.md and DISCOVERY.md to implement the planned changes locally, leaving the remote GitHub repository untouched until you explicitly close the issue.
Rewrite planning documents instead of appending changelogs whenever your project understanding evolves during the create, edit, or plan phases. This DRY discovery approach ensures DISCOVERY.md and PLAN.md always represent the current state, preventing outdated historical entries from cluttering your workflow.
tonombConfigure issue trackers, triage labels, and documentation layouts across GitHub, GitLab, and local markdown.
khwerhahnClose GitHub issues, linked pull requests, and feature branches.
phillipganAutomates GitHub issue management and pull request creation for CI workflows.
thewoolleymanAutomate GitHub issue creation, triage, and project board synchronization with swarm coordination.
