github-swarm-issue-3-progress-tracking
Sub-skill of github-swarm-issue: 3. Progress Tracking (+3).
Best use case
github-swarm-issue-3-progress-tracking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of github-swarm-issue: 3. Progress Tracking (+3).
Teams using github-swarm-issue-3-progress-tracking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/3-progress-tracking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-swarm-issue-3-progress-tracking Compares
| Feature / Agent | github-swarm-issue-3-progress-tracking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of github-swarm-issue: 3. Progress Tracking (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 3. Progress Tracking (+3)
## 3. Progress Tracking
```bash
# Track issue progress
track_progress() {
local ISSUE_NUM=$1
# Get current issue state
ISSUE=$(gh issue view $ISSUE_NUM --json body,labels)
BODY=$(echo "$ISSUE" | jq -r '.body')
# Count completed vs total tasks
*See sub-skills for full details.*
## 4. Issue Comment Commands
Use these commands in issue comments:
```markdown
<!-- Analyze issue and suggest approach -->
/swarm analyze
<!-- Decompose into subtasks -->
/swarm decompose 5
<!-- Assign specific agent type -->
*See sub-skills for full details.*
## 5. Automated Triage
```bash
# Triage unlabeled issues
triage_issues() {
# Get unlabeled issues
gh issue list --label "" --json number,title,body | \
jq -r '.[] | @base64' | while read -r encoded; do
ISSUE=$(echo "$encoded" | base64 -d)
NUM=$(echo "$ISSUE" | jq -r '.number')
TITLE=$(echo "$ISSUE" | jq -r '.title')
BODY=$(echo "$ISSUE" | jq -r '.body')
*See sub-skills for full details.*
## 6. Stale Issue Management
```bash
# Process stale issues
manage_stale_issues() {
# Get issues not updated in 30 days
STALE_DATE=$(date -d '30 days ago' '+%Y-%m-%d')
gh issue list --state open --json number,title,updatedAt | \
jq -r ".[] | select(.updatedAt < \"$STALE_DATE\") | .number" | \
while read -r num; do
# Check if already marked stale
*See sub-skills for full details.*Related Skills
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
tax-filing-session-setup-with-github-tracking
Structured workflow for preparing and tracking a tax filing session using prepared documents, task checklist, and GitHub issue cross-referencing
tax-filing-session-setup-with-github-traceability
Structured workflow for setting up a multi-file tax filing session with GitHub issue tracking and prepared-file validation
staged-issue-tree-creation-with-deduplication
Pattern for creating hierarchical GitHub issue trees from phased project plans while checking for duplicate/overlapping issues
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
plan-gated-issue-implementation
Workflow for executing pre-approved GitHub issues with mandatory validation checkpoints
github-issue-structure-for-personal-finance-tracking
Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
plan-draft-review-artifact-truthfulness-and-issue-body-alignment
Keep plan drafts truthful during adversarial review loops by verifying real provider artifact state on disk and aligning the GitHub issue body to the bounded plan tranche before claiming approval-readiness.
parallel-llm-wiki-gap-to-issues
Use parallel subagents to mine remaining LLM-wiki/document-intelligence gaps, de-duplicate against existing GitHub issues, then create only the strongest bounded follow-on issues.
llm-wiki-ecosystem-gap-to-issues
Review the workspace-hub LLM-wiki/document-intelligence ecosystem, identify high-leverage gaps, and create grounded GitHub feature issues without duplicating existing work.
interactive-issue-execution-worktree-guardrails
Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.
github-actions-trigger-and-shell-gotchas
Prevent false verification gaps in GitHub Actions by checking push path filters, shell compatibility, and shared CI environment failures before concluding a workflow fix worked or failed.