<< All versions

Skill v1.0.3

currentAutomated scan
khaneliman/khanelinix/github-toolkit

fix(blender): use bounded visual iterations

──Details
PublishedSeptember 17, 2026 at 01:31 AM
Content Hashsha256:9b5ef893f81c9439...
Git SHAc1bd78a88154
Compare with v1.0.2
──Files
Files (1 file, 2.9 KB)
SKILL.md2.9 KBactive
SKILL.md · 54 lines · 2.9 KB

version: "1.0.3" name: github-toolkit description: GitHub maintainer queues; issue discovery, triage, and creation; PR creation, walkthroughs, and stacking; review authoring and feedback; CI checks and fixes using gh CLI. Use for read or write work on GitHub issues, PRs, stacks, reviews, or checks.


GitHub Toolkit

Route to one mode and load only named reference:

  1. issue-creation: draft or explicitly create issue. Read

issue-creation.md.

  1. pull-request-creation: draft or explicitly create pull request. Read

pull-request-creation.md.

  1. pr-stacking: create, inspect, restructure, or merge dependent pull

requests as a GitHub stack. Read pr-stacking.md.

  1. issue-discovery: search, filter, rank, or summarize many issues. Read

issue-discovery.md.

  1. issue-triage: classify target issue and draft next-step guidance. Read

issue-triage.md.

  1. pr-review: review target, then inspect, create, update, or delete

current-actor reviews when explicitly requested. Read pr-review.md.

  1. pr-feedback: inspect or address existing review comments. Read

pr-feedback.md.

  1. ci-fix: diagnose failing CI and implement and verify requested fixes.

Read ci-fix.md.

  1. maintainer-queue: collect a bounded repository queue, rank evidenced next

actions, and route selected items. Read maintainer-queue.md.

  1. pr-merge: merge an authorized PR or finish post-merge closeout. Read

pr-merge.md. Use its closeout after stack merges too.

  1. pr-walkthrough: explain a PR or prepare a reviewer guide. Read

pr-walkthrough.md.

If intent is unclear, ask for mode before GitHub writes or source edits.

Shared Rules

  • Read repository contributor docs, local instructions, and matching issue/PR

template before drafting or publishing.

  • Treat GitHub writes as separate authority: inspect and draft by default;

create, edit, comment, label, close, submit, or resolve only when requested.

  • PR URL inputs accept https://github.com/... only. Do not use these helpers

for GitHub Enterprise until hostname binding is implemented.

  • Write public prose like teammate: specific evidence and direct request, no

generic significance claims, canned acknowledgement, or repeated detail.

  • Use git-toolkit change-stack mode to decide commit/branch slices and review

units. Use pr-stacking mode here to execute those slices as a GitHub stack.

  • Call out destructive Git risk before reset, rewrite, force-push, or remote

branch deletion. Route verified task-owned local cleanup to git-toolkit; honor existing cleanup authority without asking again.

← v1.0.2All versions