Automate GitHub issue-driven workflows with phase notes and PR linking.
npx skills add https://github.com/hmjn023/solid-imager --skill issue-driven
Please help me install this Agent Skill. Skill: issue-driven Source: https://github.com/hmjn023/solid-imager/tree/main/.opencode/skills/issue-driven Command: npx skills add https://github.com/hmjn023/solid-imager --skill issue-driven
GitHub Issues are used as the primary source of truth for task definitions and progress auditing in an autonomous development workflow, enabling teams to document investigations, plans, implementations, and reviews within each issue lifecycle.
Create or select a GitHub issue to begin the workflow and follow Investigate, Plan, Implement, Review, Submit, and Done steps, posting notes and moving the issue through stages as you go.
High-intent search queries and answers about installing and using this skill.
Automating development workflows with GitHub Issues requires defining tasks and tracking progress through structured phases. This Skill uses issues to drive the lifecycle, logging notes at each stage from investigation to submission, and linking pull requests to maintain full audit trails.
An issue-driven development workflow uses GitHub Issues as task definitions and audit trails. It tracks progress by generating phase-specific logs—Investigation, Plan, Implementation, and Review—within each issue, ensuring decision-making and changes are fully traceable.
To link a pull request to a GitHub issue automatically, the workflow moves the issue through its lifecycle stages and submits changes via PRs. This creates a direct connection between the implementation and the original task definition for accountability.
Yes, this workflow supports structured issue-based progress tracking by enforcing clear guardrails. It moves issues through Investigate, Plan, Implement, Review, Submit, and Done phases, satisfying requirements for traceable workflow automation with phase-specific logs.
Using GitHub Issues for autonomous workflow automation requires strict adherence to the defined lifecycle phases. The process depends on generating phase-specific notes and linking PRs, meaning workflows outside this structured Investigate to Done path may not be fully traceable or supported.
No specific dependencies or components are required to start the issue-driven workflow. You only need a GitHub issue to begin, following the defined Investigate, Plan, Implement, Review, Submit, and Done steps to post notes and track the lifecycle.
lluppesmsSearch GitHub repository issues assigned to the user and suggest prioritization.
biz-StreamCreates GitHub pull requests after a successful build and push.
awinogradovAutomate development workflows from planning through pull request monitoring.
juvenalConvert spec-kit tasks.md task items into GitHub issues.
