Agent skill

Gh Triage Repo

by FUjr in FUjr/homeassistant-openwrt-ubus

Triage and maintain this GitHub repository with the GitHub CLI.

GPL-3.0Auto-check passedDevelopment

Install Gh Triage Repo

skills CLI
$ npx skills add FUjr/homeassistant-openwrt-ubus --skill gh-triage-repo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FUjr/homeassistant-openwrt-ubus gh-triage-repo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FUjr/homeassistant-openwrt-ubus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gh-triage-repo .claude/skills/gh-triage-repo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gh-triage-repo
GitHub stars
118
Token cost
~1.2k tokens
SKILL.md length
514 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
GPL-3.0

At a glance

Triage and maintain this GitHub repository with the GitHub CLI.

  • Works in 4 steps: Run gh auth status before GitHub… → Prefer an existing authenticated session… → Never request that a token be pasted… → …
  • Review recent issues
  • SKILL.md covers Authenticate Safely, Discover Current Work, Ask for Disposition and Apply Approved Actions, plus 2 more sections
  • Calls gh and git; needs GH_TOKEN

What it does

Gh Triage Repo is an agent skill from FUjr/homeassistant-openwrt-ubus. Triage and maintain this GitHub repository with the GitHub CLI. Use when asked to fetch or review recent issues or pull requests, identify duplicates, ask the maintainer for a disposition on each item, post comments, add labels, close issues or PRs, merge approved PRs, or prepare repository changes under protected-main rules.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: A custom Home Assistant integration that connects to OpenWrt routers via the ubus interface to provide device tracking and system monitoring capabilities. The licence is GPL-3.0.

When your agent uses it

  • Review recent issues
  • Identify duplicates
  • Ask the maintainer for a disposition on each item
  • Merge approved PRs

Example prompts

  • “/gh-triage-repo”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Run gh auth status before GitHub operations.
  2. Prefer an existing authenticated session or a GH_TOKEN already exported by the user.
  3. Never request that a token be pasted into chat, place a token in a command line, print it, or write it to repository files. If…
  4. Resolve the repository from git remote get-url origin; do not assume an owner or repository name.

What it can do on your machine

Read from SKILL.md and the folder at commit adaebdf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gh Triage Repo loads about 1.2k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 514 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FUjr/homeassistant-openwrt-ubus at commit adaebdf, republished under its GPL-3.0 licence (© FUjr). 514 words, ~1,200 tokens.

Download SKILL.mdSave it as .claude/skills/gh-triage-repo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gh-triage-repo
description
Triage and maintain this GitHub repository with the GitHub CLI. Use when asked to fetch or review recent issues or pull requests, identify duplicates, ask the maintainer for a disposition on each item, post comments, add labels, close issues or PRs, merge approved PRs, or prepare repository changes under protected-main rules.

GitHub Repository Triage

Use gh to turn the repository's current issues and pull requests into explicit maintainer decisions, then apply only the approved actions.

Authenticate Safely

  1. Run gh auth status before GitHub operations.
  2. Prefer an existing authenticated session or a GH_TOKEN already exported by the user.
  3. Never request that a token be pasted into chat, place a token in a command line, print it, or write it to repository files. If authentication is missing, ask the user to run gh auth login or export GH_TOKEN in their terminal.
  4. Resolve the repository from git remote get-url origin; do not assume an owner or repository name.

Discover Current Work

Start read-only. Preserve unrelated working-tree changes.

sh
git status -sb
gh issue list --limit 10 --state open --json number,title,author,createdAt,updatedAt,url,labels,body
gh pr list --limit 10 --state open --json number,title,author,createdAt,updatedAt,url,labels,body,headRefName,baseRefName,isDraft,mergeStateStatus,reviewDecision

For each likely issue duplicate, inspect comments and search all states before choosing a canonical item:

sh
gh issue view NUMBER --comments --json number,title,body,comments,state,labels,url
gh issue list --state all --search "DISTINCTIVE TERMS" --json number,title,state,url,labels
gh label list --limit 100 --json name,description

For each PR, inspect the actual patch and checks rather than relying on its description:

sh
gh pr view NUMBER --comments --json number,title,body,comments,files,commits,statusCheckRollup,mergeStateStatus,reviewDecision,url,author,headRefName,baseRefName,isDraft
gh pr diff NUMBER --patch
gh pr checks NUMBER

Ask for Disposition

Summarize each item in the user's language, but draft public GitHub comments in English unless requested otherwise. Ask for a decision per item before any GitHub write.

Offer only relevant choices, such as:

  • Issue: investigate/fix, request logs, documentation answer, duplicate, wontfix, or close as resolved.
  • PR: verify and merge, request changes/tests, wait for draft completion, superseded/close, or manually adopt selected changes.

State the proposed canonical issue or fixing PR for every duplicate. Do not mark symptomatically similar reports as duplicates without evidence from bodies, comments, logs, or code history.

Apply Approved Actions

Re-read item state immediately before mutation so concurrent updates are not missed.

For a confirmed duplicate, use the existing duplicate label, post a concise comment linking the canonical issue or merged PR, then close:

sh
gh issue edit NUMBER --add-label duplicate
gh issue close NUMBER --comment "Closing this as a duplicate of #CANONICAL. ..."

For issue guidance, state the diagnosis, exact user action, relevant documentation, and whether the issue remains open. Avoid promising unimplemented work.

For PRs:

  1. Keep drafts open unless the maintainer explicitly chooses otherwise.
  2. Validate the changed behavior locally in proportion to risk.
  3. Preserve author attribution by merging the PR rather than recreating an equivalent commit when practical.
  4. Comment before merge/close with the result and any test evidence.
  5. Use the repository's accepted merge method; default to squash only when no repository convention says otherwise.
Show full SKILL.md (150 more words)Show less

Respect Protected Main

Never implement repository file changes directly on main.

  1. Confirm a clean or understood worktree with git status -sb.
  2. Fetch and create a focused branch from origin/main:
sh
git fetch origin
git switch -c TYPE/SHORT-DESCRIPTION origin/main
  1. Edit with scoped changes, validate, commit, push the branch, and open a PR.
  2. Do not overwrite, stash, reset, or discard unrelated user changes. If they block branch creation, stop and explain the conflict.
  3. After merge, fetch and verify local/remote status. Do not force-push protected branches.

Verify and Report

After writes, query GitHub again and report concrete outcomes:

  • Final state and labels for every changed issue.
  • Final state, merge commit, and checks for every changed PR.
  • Canonical item retained for duplicate groups.
  • Branch and PR URL for repository changes.
  • Local git status -sb; the worktree should be clean unless intentional changes remain.

Keep comments factual and concise. Never expose authentication material in updates or the final response.

© FUjr, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/gh-triage-repo of FUjr/homeassistant-openwrt-ubus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit adaebdf

Compare with similar skills

Gh Triage Repo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gh Triage Repo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gh Triage Repo this skillFUjr/homeassistant-openwrt-ubus118—~1.2kAutomated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

Works with

Categories

Questions about Gh Triage Repo

What does Gh Triage Repo do?

Triage and maintain this GitHub repository with the GitHub CLI. Gh Triage Repo is an agent skill from FUjr/homeassistant-openwrt-ubus. Triage and maintain this GitHub repository with the GitHub CLI.

When should I use Gh Triage Repo?

Gh Triage Repo fits situations like: review recent issues; identify duplicates; ask the maintainer for a disposition on each item; merge approved PRs.

How do I install Gh Triage Repo in Claude Code?

Run `npx skills add FUjr/homeassistant-openwrt-ubus --skill gh-triage-repo -a claude-code`. Or copy the skill folder (.agents/skills/gh-triage-repo in FUjr/homeassistant-openwrt-ubus) into .claude/skills/gh-triage-repo in your project. Claude Code loads it when a task matches its description.

How do I install Gh Triage Repo in Codex?

Run `npx skills add FUjr/homeassistant-openwrt-ubus --skill gh-triage-repo -a codex`. Or copy the skill folder (.agents/skills/gh-triage-repo in FUjr/homeassistant-openwrt-ubus) into .agents/skills/gh-triage-repo in your project. Codex loads it when a task matches its description.

Can I use Gh Triage Repo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FUjr/homeassistant-openwrt-ubus --skill gh-triage-repo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-triage-repo, .gemini/skills/gh-triage-repo, .github/skills/gh-triage-repo and .opencode/skills/gh-triage-repo in your project.

What does Gh Triage Repo need to run?

Going by SKILL.md and its folder, Gh Triage Repo needs the command-line tools its instructions call (gh and git) and credentials named GH_TOKEN.

Does Gh Triage Repo access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gh Triage Repo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gh Triage Repo use?

Gh Triage Repo is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gh Triage Repo use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gh Triage Repo?

Skills that share tags, products or a category with Gh Triage Repo: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gh Triage Repo?

FUjr (a GitHub user) maintains it in FUjr/homeassistant-openwrt-ubus, which has 118 GitHub stars. The repository was last updated on July 27, 2026.

Source: FUjr/homeassistant-openwrt-ubus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.