skills.rest
finlaysonstudio
finlaysonstudioOFFICIAL
Explore all skills by this author →
GitHub

ticket

Guide GitHub issue handling through fetch, validate, test, plan, branch, implement, and report workflows.

2|Updated Mar 15, 2024
Search Tags:#workflow#planning#testing#github#branching#ticket#issue-management
One-click install
npx skills add https://github.com/finlaysonstudio/jaypie --skill ticket-finlaysonstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/finlaysonstudio/jaypie/tree/main/.claude/skills/ticket
Command: npx skills add https://github.com/finlaysonstudio/jaypie --skill ticket-finlaysonstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workflows for handling a GitHub issue end-to-end: fetch, validate, test, plan, branch, implement, and report.

Core Features & Use Cases

  • End-to-end issue lifecycle: fetch the issue, validate it's not already fixed or invalid, plan a fix or feature, create a branch (fix/issue-NNN or feat/issue-NNN), implement changes, test, and report results.
  • Structured planning and governance: provide a clear plan before implementing to ensure traceability and repeatability.
  • Reporting and optional steps: generate a summary report and optionally run /prepare or /shepherd when requested.

Quick Start

Fetch a GitHub issue via MCP and follow the guided workflow to validate, plan, implement, and report.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I manage a GitHub issue workflow from start to finish?▼

A GitHub issue workflow can be managed end-to-end by sequentially fetching, validating, testing, planning, branching, implementing, and reporting changes. This structured approach ensures traceability and reproducible planning for software maintenance and feature work.

What is the best way to create branches for GitHub issue tracking?▼

Creating branches for GitHub issue tracking is best handled by using structured naming conventions like fix/issue-NNN or feat/issue-NNN. This ensures version-controlled branches are directly tied to the validated issue for clear traceability.

Do I need to validate a GitHub issue before planning a fix?▼

Validating a GitHub issue before planning a fix is required to ensure the issue is not already resolved or invalid. This prevents redundant work and confirms the problem requires a new version-controlled branch.

Can I generate a report after implementing changes for a GitHub issue?▼

Generating a report after implementing changes for a GitHub issue is supported as the final step in the workflow. It produces a documented summary of the testing and implementation results for quality control purposes.

Does the GitHub issue workflow support optional commands for quality control?▼

The GitHub issue workflow supports optional shepherd and prepare commands for quality control. These can be run when requested to provide additional governance and traceability during the implementation phase.

Related Skills

Explore More Software Engineering Skills→
kalamdbkalamdb
48

speckit-taskstoissues

Convert spec-kit project tasks into dependency-ordered GitHub issues.

Official
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
matiaszanollimatiaszanolli
6

fix-issue

Automate GitHub issue fixes in the midi2nes repository with Python scripting.

Community
Advanced
qauth-labsqauth-labs
23

gh-issues

Automate GitHub issue creation, viewing, editing, and lifecycle management.

Official
Intermediate