skills.rest
graysurf
graysurfCOMMUNITY
Explore all skills by this author →
GitHub

report-plan-issue-finding

Create labeled GitHub issues to file plan-issue findings in a central tracker.

Updated Aug 27, 2026
Search Tags:#automation#github#issue#triage#plan-tracking#plan-issue
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill report-plan-issue-finding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-plan-issue-finding
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/issue/skills/report-plan-issue-finding/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill report-plan-issue-finding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File plan-issue findings into a central tracker by converting observed problems in plan-tracking workflows into a durable, labeled GitHub issue. The finding is recorded and tracked without needing to file from the tracker repo and the skill owns only the issue lifecycle (open, dedup, comment, close).

Core Features & Use Cases

  • Open labeled GitHub issues in the canonical tracker from any repository where a finding appears.
  • Deduplicate against existing open findings, comment on matches, and close issues when upstream fixes land.
  • End-to-end governance of the finding lifecycle: open, triage, comment, and close, while the actual fix is implemented upstream in agent-runtime-kit or nils-cli.

Quick Start

Create a new plan-issue finding in the tracker using forge-cli with a descriptive title and full body.

Frequently Asked Questions about report-plan-issue-finding

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

FAQPage Schema
How do I automatically create GitHub issues from plan-tracking findings?▼

You can automatically create GitHub issues from plan-tracking findings by using this skill to file detected problems as labeled issues directly into a central tracker repository.

What is the best way to deduplicate triage issues in a GitHub tracker?▼

The best way to deduplicate triage issues is to check existing open findings in the tracker, add a comment to the matching issue, and close duplicates when an upstream fix lands.

Do I need forge-cli and jq to file plan-issue findings to GitHub?▼

Yes, you need forge-cli and jq installed, along with authenticated access to the central tracker, to generate and manage labeled GitHub issues from plan-issue workflows.

Can I open tracker issues from any repository in my plan-tracking workflow?▼

Yes, you can open labeled tracker issues from any repository that the central tracker monitors, applying across skill, CLI, provider, driver, and catalog surfaces.

Are there strict title-length or labeling rules for automated GitHub issue creation?▼

Yes, the skill enforces strict title-length and labeling rules when creating GitHub issues to ensure consistent triage and governance across the plan-tracking workflow.

Related Skills

Explore More Software Engineering Skills→
tanyagraytanyagray

bitbucket-setup

Install and configure the Bitbucket CLI for Bitbucket Cloud workflows.

Community
Intermediate
JnusoJnuso

openclaw-pr-maintainer

Automates OpenClaw pull-request and issue triage with labeling and comment drafting.

Community
Intermediate
SimHackerSimHacker
49

debugging

Systematically debug issues by hypothesizing, testing, and tracking evidence.

Community
Advanced
DarkArty07DarkArty07
3

github-issues

Manage GitHub issue lifecycle and bulk triage via CLI or REST API.

Community
Intermediate