agentleFS
Sign inStart free
akunzaiakunzai/agent-skills/skills/github-epic/SKILL.md

github-epic

Skill5 starsChanged 54 days agoMITView on GitHub

Use ONLY when a git repository is hosted on GitHub to create, structure, or link GitHub epics, sub-issues, and dependency relationships.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify GitHub hosting (git remote get-url origin).

    line 15
  2. Very specific:

    Auto-close: Use Closes #N, Fixes #N, or Resolves #N solely when merging auto-closes issue #N.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Epic & Sub-issues

Manage multi-issue epics, parent-child task hierarchies, and blocking dependencies natively on GitHub.

Preflight & Hosting Check

Verify GitHub hosting (git remote get-url origin). For custom domains needing self-hosted GHES detection, see hosting-detection.md.

Native Wiring (GitHub API)

GitHub supports native sub-issue hierarchies and issue dependency links via gh api using numeric database IDs (not issue numbers).

1. Database ID Lookup

gh api repos/<owner>/<repo>/issues/<issue_number> --jq .id

2. Link Sub-issue to Epic

gh api --method POST repos/<owner>/<repo>/issues/<parent_number>/sub_issues \
  -F sub_issue_id=<child_db_id>

3. Link Blocked-by Dependency

gh api --method POST repos/<owner>/<repo>/issues/<child_number>/dependencies/blocked_by \
  -F issue_id=<blocker_db_id>

Issue Linking Conventions

  • Auto-close: Use Closes #N, Fixes #N, or Resolves #N solely when merging auto-closes issue #N.
  • Part-of: Tag Part of #N or See #N for multi-PR epics. Never pair closing keywords with tracking issues. GitHub matches those tokens even inside negation — do not write Closes #N (or Fix/Resolve) next to a tracking issue to say not to close it.
  • Dual References: Combine native API wiring with markdown prose links for cross-interface readability.

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