How do I install the Richardgill Nix Issues skill?

Run npx skillmds@latest add tomevault-io/richardgill-nix-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Richardgill Nix Issues skill do?

Issue Management It is listed under Coding & Dev Tools on SkillMD.

Is Richardgill Nix Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Richardgill Nix Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Richardgill Nix Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Richardgill Nix Issues?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Richardgill Nix Issues by tomevault-io

Name: Richardgill Nix Issues
Author: tomevault-io

File contents

Issue Management

Manage the project's persistent work tracker in thoughts/shared/issues/.

Issue & Plan Storage

Issues and plans are tracked in ./issues/ with numbered phases:

./issues/
├── 10-phase-name/           # Single issue = flat folder
│   └── plan.md
├── 20-another-phase/
│   ├── plan.md
│   └── design.md          # Optional
├── 30-multi-issue-phase/    # Multiple parallel issues = nested
│   ├── feature-a/
│   │   ├── plan.md
│   │   └── design.md
│   └── feature-b/
│       └── plan.md
└── done/                    # Completed issues moved here

Conventions:

Single issue phase → NN-phase-name/ (flat)
Multi-issue phase → NN-phase/issue-name/ (nested, all parallel)
Gaps in numbers (10, 20...) = room to insert phases later
Each issue has plan.md + optional design.md
Completed issues → move to done/

Workflow:

Work through phases in order (10 → 20 → 30...)
Within a phase folder, pick any issue - they're independent
Read issue's plan.md for scope

Commands

List Active Issues

ls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/

Show What's Next

ls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/ | head -1

Create Issue

Check existing phases: ls thoughts/shared/issues/
Pick phase number (use gaps like 10, 20, 30 for flexibility)
Create folder:
- Single issue: thoughts/shared/issues/NN-issue-name/
- Multi-issue phase: thoughts/shared/issues/NN-phase/issue-name/
Add plan.md with scope and implementation details
Optionally add design.md for design notes

Complete Issue

Move to done when fully implemented:

mkdir -p thoughts/shared/issues/done
mv thoughts/shared/issues/NN-issue-name thoughts/shared/issues/done/

Show Progress

echo "Active:" && ls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/ | wc -l
echo "Done:" && ls -1d thoughts/shared/issues/done/*/ 2>/dev/null | wc -l

Triage/Prioritize

Review all phases: ls -la thoughts/shared/issues/

Check recent work to identify completed issues:

git log --oneline -20
git diff main~10..main --stat

Move completed issues to done
Renumber folders to reorder priority
Move items between phases as needed
Update any plan.md files with new scope

$ARGUMENTS

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: richardgill-nix-issuesdescription: Issue Management---# Issue ManagementManage the project's persistent work tracker in `thoughts/shared/issues/`.## Issue & Plan StorageIssues and plans are tracked in `./issues/` with numbered phases:```./issues/├── 10-phase-name/ # Single issue = flat folder│ └── plan.md├── 20-another-phase/│ ├── plan.md│ └── design.md # Optional├── 30-multi-issue-phase/ # Multiple parallel issues = nested│ ├── feature-a/│ │ ├── plan.md│ │ └── design.md│ └── feature-b/│ └── plan.md└── done/ # Completed issues moved here```**Conventions:**- **Single issue phase** → `NN-phase-name/` (flat)- **Multi-issue phase** → `NN-phase/issue-name/` (nested, all parallel)- **Gaps in numbers** (10, 20...) = room to insert phases later- Each issue has `plan.md` + optional `design.md`- **Completed issues** → move to `done/`**Workflow:**1. Work through phases in order (10 → 20 → 30...)2. Within a phase folder, pick any issue - they're independent3. Read issue's `plan.md` for scope## Commands### List Active Issues```bashls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/```### Show What's Next```bashls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/ | head -1```### Create Issue1. Check existing phases: `ls thoughts/shared/issues/`2. Pick phase number (use gaps like 10, 20, 30 for flexibility)3. Create folder: - Single issue: `thoughts/shared/issues/NN-issue-name/` - Multi-issue phase: `thoughts/shared/issues/NN-phase/issue-name/`4. Add `plan.md` with scope and implementation details5. Optionally add `design.md` for design notes### Complete IssueMove to done when fully implemented:```bashmkdir -p thoughts/shared/issues/donemv thoughts/shared/issues/NN-issue-name thoughts/shared/issues/done/```### Show Progress```bashecho "Active:" && ls -1d thoughts/shared/issues/*/ 2>/dev/null | grep -v done/ | wc -lecho "Done:" && ls -1d thoughts/shared/issues/done/*/ 2>/dev/null | wc -l```### Triage/Prioritize1. Review all phases: `ls -la thoughts/shared/issues/`2. Check recent work to identify completed issues: ```bash git log --oneline -20 git diff main~10..main --stat ```3. Move completed issues to done4. Renumber folders to reorder priority5. Move items between phases as needed6. Update any `plan.md` files with new scope$ARGUMENTS---> Converted and distributed by [TomeVault](https://tomevault.io/claim/richardgill) — claim your Tome and manage your conversions.

Frequently asked questions

Richardgill Nix Issues