# Descoped LLM Skills Github Issues Workflow

> GitHub Issues Workflow

- Skill: `tomevault-io/descoped-llm-skills-github-issues-workflow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/descoped-llm-skills-github-issues-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/descoped-llm-skills-github-issues-workflow/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/descoped-llm-skills-github-issues-workflow

---


# GitHub Issues Workflow

Bootstrap an issue-driven development workflow for monorepo projects.

## What This Skill Produces

1. **GitHub Label Setup Script** — `scripts/github/setup-labels.sh`
2. **Issue Templates** — `.github/ISSUE_TEMPLATE/{default,bug,feature}.md`
3. **PR Template** — `.github/PULL_REQUEST_TEMPLATE.md`
4. **Claude Code Commands** — `.claude/commands/{PREFIX}-{issue,start,review,address}.md`

## Workflow

### Phase 1: Gather Project Information

Ask the user for:

1. **GitHub repo** (e.g., `org/repo-name`)
2. **Project short name** — used as prefix for Claude commands (e.g., `frk` produces `/frk-issue`, `/frk-start`)
3. **Workspace areas** — which modules exist and their paths. Ask:
   - What backend tech? (Rust, Python, Go, Java, or none)
   - What frontend tech? (React, Next.js, Svelte v5, or none)
   - Mobile apps? (iOS, Android, or none)
   - Tooling crates/packages? (Rust crates, Python packages, Go modules, etc.)
   - Infrastructure/DevOps? (Docker, CI/CD, etc.)
4. **Architecture style** — if applicable (hexagonal, layered, clean, microservices, monolith, etc.)
5. **Branching strategy** — main branch name (`main` or `master`), branch naming convention

Consult `references/tech-stacks.md` for tech-specific check commands, package managers, and workspace patterns.

### Phase 2: Generate Labels Script

Generate `scripts/github/setup-labels.sh` using the script template in `scripts/generate-labels.sh`.

Customize area labels based on the project's actual workspace areas. Keep type, priority, and status labels standard.

### Phase 3: Generate Issue Templates

Copy and customize templates from `assets/issue-templates/`:

- `default.md` — General issue (solution-agnostic, focus on WHAT/WHY not HOW)
- `bug.md` — Bug report with environment details
- `feature.md` — Feature request with user story format

Replace area checkboxes with the project's actual workspace areas.

### Phase 4: Generate PR Template

Copy and customize `assets/pull-request-template.md`. Replace:
- Area checkboxes with project's workspace areas
- Testing checklist with tech-appropriate check commands (from `references/tech-stacks.md`)

### Phase 5: Generate Claude Code Commands

Generate four slash commands in `.claude/commands/` using the project short name as prefix. Consult `references/commands-guide.md` for the full workflow specification and customize per-project.

| Command | File | Purpose |
|---------|------|---------|
| `/{PREFIX}-issue` | `{PREFIX}-issue.md` | Create GitHub issue with proper labels and templates |
| `/{PREFIX}-start` | `{PREFIX}-start.md` | Full issue-to-PR workflow: branch, design doc, task file, implement, PR |
| `/{PREFIX}-review` | `{PREFIX}-review.md` | Structured PR review with tech-specific checklist |
| `/{PREFIX}-address` | `{PREFIX}-address.md` | Address PR/issue feedback systematically |

Key customizations per project:
- Repo name in all `gh` commands
- Workspace areas table with paths and check commands
- Tech-specific quality checks (from `references/tech-stacks.md`)
- Architecture-specific review criteria

### Phase 6: Run Label Setup

Ask if the user wants to run the label setup script now:
```bash
bash scripts/github/setup-labels.sh
```

### Phase 7: Commit

Stage and commit all generated files:
```bash
git add scripts/github/ .github/ .claude/commands/
git commit -m "chore: add GitHub workflow infrastructure"
```

## Key Design Principles

- **Solution-agnostic issues** — Issues describe WHAT and WHY, never HOW. No file paths or code specifics in issues.
- **Self-contained design docs** — `.claude/issues/issue-N/design.md` copies all specs verbatim; never references external files by path.
- **Task tracking** — `.claude/issues/issue-N/task.md` with checkbox tasks checked off during implementation.
- **Issue lifecycle** — Active work in `.claude/issues/`, archived to `.claude/history/` after PR merge.
- **Conventional commits** — `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`
- **No AI attribution** — Never add `Co-Authored-By: Claude` or similar to commits.

---
> Source: [descoped/llm-skills](https://github.com/descoped/llm-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->