skills.rest
tonitangpotato
tonitangpotatoCOMMUNITY
Explore all skills by this author →
GitHub

project-issues

Track cross-project issues in .gid/docs/issues-index.md and .gid/issues/ directories.

5|1|Updated Mar 9, 2026
Search Tags:#automation#workflow#improvement#issue#tracking#project-management#bug
One-click install
npx skills add https://github.com/tonitangpotato/rustclaw --skill project-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-issues
Source: https://github.com/tonitangpotato/rustclaw/tree/main/skills/project-issues
Command: npx skills add https://github.com/tonitangpotato/rustclaw --skill project-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, manage, and fix issues across multiple projects in a centralized, auditable manner to prevent problems from slipping through the cracks.

Core Features & Use Cases

  • Centralized issue tracking under .gid/issues per project, with a global issues-index.md overview.
  • Support for per-issue directories (ISS-NNN) for requirements, design, tasks, and progress documentation.
  • End-to-end workflow for creating, updating statuses, logging progress, and generating cross-project dashboards.

Quick Start

Record a new issue by describing it to the agent and saving it under the project's .gid/issues/ISS-001/ directory.

Frequently Asked Questions about project-issues

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

FAQPage Schema
How do I track cross-project issues and bugs in a centralized format?▼

You can track cross-project issues by organizing bugs, improvements, and tasks into a centralized issues-index.md file. This approach maintains issue lifecycles in a machine-readable format to prevent problems from slipping through the cracks.

How do I manage issue lifecycles using YAML frontmatter?▼

Managing issue lifecycles involves applying a YAML frontmatter schema for ISS entries. The system parses issue headers to support end-to-end workflows for creation, assignment, verification, and closure across project directories.

What is the best way to log progress and update statuses for project issues?▼

The best way to log progress and update statuses is through structured issue directories. You can record requirements, design, and tasks within per-issue ISS-NNN folders, updating status changes and generating cross-project dashboards.

Can I generate cross-project dashboards for bugs and improvements?▼

Yes, you can generate cross-project dashboards by parsing the centralized issues-index.md and individual issue directories. This provides an auditable overview of all tracked bugs, improvements, and tasks across your workspace.

Do I need specific project directory structures for issue tracking?▼

You need projects to maintain issue lifecycles under .gid/docs/issues-index.md or complex workspaces under .gid/issues/. This directory structure supports simple issue records and detailed per-issue documentation.

How to record a new issue and save it within a project workspace?▼

To record a new issue, describe it to the agent and save the details under the project's .gid/issues/ISS-001/ directory. This creates a structured entry that integrates with the global issues index.

Related Skills

Explore More Product & Management Skills→
tonitangpotatotonitangpotato
5

project-init

Automate creation of a standardized .gid/ project skeleton with graph.yml and config.yml.

Community
Intermediate
lsnackermanlsnackerman
42

task

Parse natural language into structured task documents with YAML frontmatter.

Community
Advanced
interactive-incinteractive-inc
1

backlog

Record, update, and plan tasks within a project backlog.

Official
Intermediate
rortan134rortan134
26

to-tickets

Convert plans or specifications into issue tickets with blocking dependencies.

Community
Advanced