Agent Skills: Github

|

UncategorizedID: i9wa4/dotfiles/github

Install this agent skill to your local

pnpm dlx add-skill https://github.com/i9wa4/dotfiles/tree/HEAD/skills/github

Skill Files

Browse the full folder contents for github.

Download Skill

Loading file tree…

skills/github/SKILL.md

Skill Metadata

Name
github
Description
|

Github

UTILITY SKILL: Apply this skill to GitHub: gh CLI usage, PR conflict resolution, commit messages, issue/PR creation, inline comments, sub-issues, review style, public surface path hygiene rules. Keep the task scoped to the requested domain and preserve existing repo conventions.

USE FOR: GitHub: gh CLI usage, PR conflict resolution, commit messages, issue/PR creation, inline comments, sub-issues, review style, public surface path hygiene rules; related file edits; verification and handoff in this skill domain.

DO NOT USE FOR: unrelated domains, broad rewrites outside the request, generated runtime outputs, or replacing repo-specific source of truth.

Boundary

This skill owns GitHub mechanics: gh usage, issue/PR state inspection, commit and PR-publication rules, inline comment mechanics, and public wording/path hygiene. It supports review workflows but does not own the guardian/critic review engine or the user-facing review-comment trigger.

Workflow

  1. Inspect the relevant files, current repo conventions, and git status.
  2. Read Preserved Guidance before changing behavior or giving detailed instructions.
  3. Before branch publication or PR creation, verify branch, upstream, base, head, and clean status; use the explicit same-name remote destination workflow described in the preserved guidance.
  4. Make the smallest scoped change that satisfies the request.
  5. Run the checks named in the preserved guidance or the nearest repo harness.
  6. Report verification results and any remaining risk.

Examples

For a request in this domain, load preserved guidance, update the relevant source, run focused checks, and summarize the result.

References

Troubleshooting

If Waza or repo validation disagrees with preserved guidance, follow the stricter rule and record the exception in the handoff.