agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/skills/github-integration/SKILL.md

github-integration

Skill2 starsChanged 31 days agoMITView on GitHub

Creates issues and pull requests with GitHub CLI or MCP when authenticated; falls back locally when unavailable

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer authenticated GitHub CLI:

    line 14
  2. Very specific:

    Check gh auth status (or GitHub MCP availability).

    line 26
  3. Distinctive:

    Create or reference a real GitHub issue for the workstream.

    line 28
  4. Very specific:

    Use a documented local issue placeholder (e.g.

    line 33
  5. Distinctive:

    Write a PR-ready description into the completion report / chat.

    line 34
  6. Distinctive:

    Do not treat missing remote PR as a Definition-of-Done failure in V0.2.

    line 36

≈ “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 Integration (Stage 1)

Use this Skill when

Creating or updating issues, opening pull requests, commenting on PRs, or checking CI status for an approved change.

Prerequisites

Prefer authenticated GitHub CLI:

gh auth status
# if needed:
gh auth login

Cursor GitHub MCP may also be enabled with repository read, issue create, PR create/comment, and CI status. Do not enable automatic merges or releases in Stage 1.

Procedure

  1. Check gh auth status (or GitHub MCP availability).
  2. If authenticated:
    • Create or reference a real GitHub issue for the workstream.
    • Push the feature branch.
    • Open a pull request with the prepared title/body and evidence links.
    • Optionally inspect CI status; do not auto-merge.
  3. If not authenticated:
    • Use a documented local issue placeholder (e.g. local/<slug>).
    • Write a PR-ready description into the completion report / chat.
    • Tell the Captain that remote issue/PR creation is blocked on GitHub auth.
    • Do not treat missing remote PR as a Definition-of-Done failure in V0.2.

Allowed Stage 1 capabilities

  • Repository reads
  • Issue creation
  • Pull-request creation and comments
  • CI status inspection

Prohibited actions

  • Automatic merges
  • Automatic releases
  • Production deploys via GitHub Actions without Captain approval

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