agentsclimarketplace

Open graphite stacks

Skill n1ddeh/fantastic-skills/open-graphite-stacks

A collection of Claude Code skills for PR workflows, code review, and project management β€” with personality.

Install
npx -y skills add n1ddeh/fantastic-skills --skill open-graphite-stacks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Discovers and displays all open Graphite stacks authored by you across your GitHub repos. Shows a simple grouped view of every stack with PR numbers, titles, and status. Use when you want to see what stacks you have open.

SKILL.md

2.6 KB, 670 tokens by cl100k_base, as published. Nobody here has run it

Discover My Open Stacks

Install path: This skill expects to be installed at ~/.claude/skills/open-graphite-stacks/. All script paths below assume this location. If installed elsewhere, adjust paths accordingly.

Finds all open PRs authored by the current user, groups them into Graphite stacks, and displays a simple overview.

Step 1: Fetch Data

Run the fetch script which handles everything β€” fetching PRs, enriching with review threads, and grouping into stacks:

~/.claude/skills/open-graphite-stacks/scripts/fetch-stacks.sh

This outputs pre-grouped JSON:

{
  "my-backend": {
    "stacks": [
      [
        { "number": 101, "title": "...", "isDraft": false, "reviewDecision": "APPROVED",
          "totalThreads": 5, "resolvedThreads": 2 },
        { "number": 102, "title": "...", ... }
      ]
    ],
    "standalone": [
      { "number": 115, "title": "...", ... }
    ]
  }
}

Each stack array is ordered trunk-to-tip. reviewDecision is one of: APPROVED, CHANGES_REQUESTED, REVIEW_REQUIRED, or "".

If all repos have empty stacks and standalone arrays, report: No open PRs found. and stop.

Step 2: Format Output

Render the JSON into this format:

## My Open Stacks

### my-backend

Stack 1:
- [1] [DRAFT] #101 feat: add billing endpoint | πŸ’¬ 2/5 | CHANGES_REQUESTED
- [2] #102 feat: add billing tests | πŸ’¬ 0/3 | APPROVED
- [3] #103 feat: billing UI integration | πŸ’¬ 1/1

Stack 2:
- [1] #110 fix: sync race condition | APPROVED

Standalone:
- #115 chore: bump dependencies | πŸ’¬ 0/2

### my-frontend

Stack 1:
- [1] #50 feat: new settings page | πŸ’¬ 3/4 | CHANGES_REQUESTED
- [2] #51 feat: settings validation

---
Summary: {total_prs} open PRs across {total_stacks} stacks and {standalone_count} standalone PRs

Rules:

  • Mark draft PRs with [DRAFT] before the PR number
  • Show review thread counts as πŸ’¬ N/M where N = resolved threads and M = total threads β€” but ONLY when totalThreads > 0. Omit entirely when 0/0
  • Show reviewDecision only if non-empty
  • Use | as delimiter between title, thread count, and review decision. Only include | segments that have content
  • Use markdown list syntax (- ) for each PR line
  • If a repo has no open PRs, omit it entirely
  • Group standalone PRs under a "Standalone" heading separate from numbered stacks
  • Keep it concise β€” no extra commentary, just the structured output

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.