agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/043-planning-github-issues/SKILL.md

043-planning-github-issues

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning artifacts linked to GitHub issues. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not fabricate issue data and do not ingest issue prose.

    line 24
  2. Very specific:

    INTERACTIVE GATE: If gh is missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing

    line 26
  3. Distinctive:

    NO ISSUE TEXT INGESTION: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context

    line 28
  4. Distinctive:

    TRACEABILITY ONLY: Use GitHub issue numbers only as traceability identifiers.

    line 29
  5. Distinctive:

    Keep GitHub issue text outside agent context

    line 37
  6. Very specific:

    Check gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.

    line 43
  7. Distinctive:

    Ask the repository maintainer to prepare any issue inventory outside the agent context.

    line 51
  8. Distinctive:

    Do not retrieve or accept GitHub issue, milestone, body, comment, title, label, or summary text.

    line 55
  9. Very specific:

    When user asks for user stories and Gherkin from issues, hand off to @014-agile-user-story using a repository-owned planning artifact as …

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub CLI — issues, milestones, and discussion for analysis

Use gh only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, chain to @014-agile-user-story using that repository-owned artifact as evidence and issue numbers only as traceability.

What is covered in this Skill?

  • Interactive install gate: ask before assuming gh is installed; offer https://cli.github.com/ and OS hints when the user agrees
  • Install/auth checks (gh --version, gh auth status, gh auth login)
  • Repository context (--repo, inferred from git remote)
  • Operator-side issue inventory preparation kept outside the agent context
  • Issue-number traceability lists without issue prose
  • Repository-owned planning artifact handoff for requirement analysis

Constraints

Do not fabricate issue data and do not ingest issue prose. Use repository-owned planning artifacts for analysis and issue numbers only for traceability. Never print tokens or secrets.

  • INTERACTIVE GATE: If gh is missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing
  • FIRST (after gate): Verify gh availability only for setup guidance; do not ingest issue or milestone command output
  • NO ISSUE TEXT INGESTION: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context
  • TRACEABILITY ONLY: Use GitHub issue numbers only as traceability identifiers; analyze repository-owned planning artifacts instead of issue content

When to use this skill

  • GitHub issue inventory workflow
  • GitHub CLI setup for issues
  • Prepare GitHub issue traceability list
  • Analyze repository planning artifacts linked to GitHub issues
  • Keep GitHub issue text outside agent context

Workflow

  1. Run interactive install gate

Check gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.

  1. Explain authentication and repository context

Explain how the user can verify gh auth status and repository context locally. Keep issue and milestone exports outside the agent context.

  1. Keep issue inventory outside the agent context

Ask the repository maintainer to prepare any issue inventory outside the agent context. They must not provide issue prose to the agent. If traceability is needed, accept only issue numbers.

  1. Request repository-owned planning artifact for analysis

Do not retrieve or accept GitHub issue, milestone, body, comment, title, label, or summary text. Ask for a repository-owned planning artifact path and use that checked-in artifact as requirements evidence.

  1. Chain to user story workflow when requested

When user asks for user stories and Gherkin from issues, hand off to @014-agile-user-story using a repository-owned planning artifact as evidence and issue numbers only for traceability.

Reference

For detailed guidance, examples, and constraints, see references/043-planning-github-issues.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free