github-issue-tracker

What This Skill Does

The github-issue-tracker skill transforms static GitHub issues into dynamic, project-managed workspaces. It enables granular tracking by injecting interactive task checklists directly into issue bodies, allowing teams to break down large features into manageable units (T-001, T-002, etc.). The skill automates progress reporting by posting standardized completion comments that capture actual versus estimated time, specific files modified, test outcomes, and links to the next task in the queue. Furthermore, it provides a structured framework for identifying blocking issues and dependencies, ensuring that progress is transparent and blockers are escalated clearly to stakeholders.

Installation

To integrate this skill into your OpenClaw environment, ensure you have the necessary permissions for the target GitHub repository. Update your .specweave/config.yaml file to include the following configuration:

• Install Command: clawhub install openclaw/skills/skills/anton-abyzov/sw-github-issue-tracker
• Source Repository: openclaw/skills
• Author: anton-abyzov

After installation, run a sync command to verify the connection between your local environment and the GitHub API.

Use Cases

• Complex Feature Rollouts: Use for long-running engineering tasks that require multiple development and QA phases.
• Team Coordination: Assign specific tasks to individual developers via @mentions within checklists to avoid overlapping work.
• Cross-Team Dependencies: Explicitly document blocking issues linked to other GitHub issues to prevent bottlenecks.
• Time Tracking: Maintain a historical log of estimated vs. actual development time for sprint retrospective analysis.

Example Prompts

1. "Analyze the current issue and break down the remaining work into a 10-task checklist with time estimates, assigning the first three to @developer1."
2. "I just finished T-005. Please post a task completion update, summarize the changes in src/api/auth.ts, and mark it as done in the checklist."
3. "Create a blocking issue report for T-012, noting that it depends on the infrastructure upgrade in issue #442."

Tips & Limitations

• Keep Task Descriptions Concise: While the system supports detail, keep task titles short to ensure the checklist remains readable on mobile displays.
• Consistency: Always link the next task in the completion comment to create a chain of progress that is easy to follow.
• Limitations: This skill relies on the GitHub API rate limits. For massive projects with thousands of tasks, consider splitting the work into multiple tracking issues rather than one giant list. Ensure your GitHub Projects board is properly configured to mirror the status of the checklists for the best visualization.