mcpField
G
github

github

github.com/i9wa4Development1288 installsUpdated 1d ago
Repository

About github

A utility skill for GitHub repository work, aimed at developers handling issues, pull requests, reviews, and publication. It emphasizes following repository guidance and conventions through scoped changes and verification.

Key features

  1. 01Guidance for gh CLI use
  2. 02Issue and pull request workflows
  3. 03Conflict resolution and inline reviews
  4. 04Commit and publication checks
  5. 05Repository path and wording hygiene

Use cases

  1. 01Inspecting issue or pull request state
  2. 02Resolving pull request conflicts
  3. 03Writing commits and publishing pull requests
  4. 04Preparing focused review comments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/i9wa4/dotfiles --skill github

After installing, type/githubin Claude Code to confirm it loaded.

Bundled filesreferences/preserved-guidance.md

Details

From the project README

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, and public surface path hygiene. 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; related file edits; verification and handoff.

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

1. Boundary

This skill owns GitHub mechanics: gh usage, issue/PR state inspection, commit and PR-publication rules, inline comments, 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.

2. 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.

3. Examples

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

4. References

5. Troubleshooting

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

Comments

Markdown supported