issue-reporter

Post formatted Markdown progress comments to GitHub Issues.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/drillan/marketschema --skill issue-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-reporter
Source: https://github.com/drillan/marketschema/tree/main/.claude/skills/issue-reporter
Command: npx skills add https://github.com/drillan/marketschema --skill issue-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically posts progress updates as comments to a relevant GitHub Issue when work milestones are completed, PRs are created, merges occur, or when explicitly requested.

Core Features & Use Cases

  • Automatically post progress reports when a milestone is reached, PR created, or an issue needs status updates.
  • Collects task completion status, changed files, and test results from your local or CI environment to format a clear, concise update.
  • Use Case: A team finishes a feature branch and wants to publish a structured progress update to the associated GitHub Issue for traceability and visibility.

Quick Start

  • Ensure your current branch name follows the pattern type/issue-number-description, e.g., feat/123-add-auth.
  • Tell Claude to post a progress update; the skill will gather Completed, Changes, Test Results, and Next Steps, then post a formatted comment on the linked Issue.

Frequently Asked Questions about issue-reporter

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

FAQPage Schema
How do I automate progress reports on GitHub Issues?

You can automate progress reporting on GitHub Issues by triggering a Skill that collects completed tasks, file changes, and test results to post a formatted Markdown summary comment when milestones complete or PRs are created.

Can I automatically post a comment to a GitHub Issue when a PR is created?

Yes, posting a comment to a GitHub Issue when a PR is created is supported automatically. The Skill identifies the target Issue from your branch name and posts a structured progress update with changes and next steps.

How do I link a git branch to a GitHub Issue for status updates?

To link a git branch to a GitHub Issue, ensure your branch name follows the pattern type/issue-number-description, such as feat/123-add-auth. The Skill reads this branch name to identify the correct Issue number for posting updates.

What information is included in an automated GitHub Issue progress update?

An automated GitHub Issue progress update includes completed tasks, file changes, test results, and next steps. This information is gathered from your local or CI environment and formatted into a clear Markdown summary comment.

When should I manually trigger a GitHub Issue progress comment?

You should manually trigger a GitHub Issue progress comment when you explicitly request a report or when a work milestone is reached. The Skill then gathers the current project status and posts the formatted update to the associated Issue.