cuozg/git-pr
skills/git-pr/SKILL.md
Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills git-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 2:54 AM160.0s2 files scanned
SKILL.md
- name:
- git-pr
- description:
- Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.
- author:
- kuozg
- version:
- 1.0
git-pr
Deep-investigate all files changed in a PR, then generate and apply a reviewer-ready title and structured description via gh pr edit.
When to Use
- Opening a new PR that needs a clear title and description
- Updating a stale or missing PR title or description before review
- Generating documentation-quality PR context for reviewers
- Automating PR metadata from a feature branch
Workflow
- Fetch — Run
gh pr difforgit diff base...HEADto get the full PR diff - Read — Read every changed file to understand the actual implementation
- Investigate — Trace cross-file dependencies, identify the root change vs cascading effects
- Draft title — Write a concise PR title in imperative or descriptive form that reflects the root change
- Draft body — Write a structured description using the template in
references/pr-description-template.md - Apply — Run
gh pr edit --title "..." --body "..."to push both fields to GitHub
Rules
- Read all changed files — do not summarize from diff hunks alone
- Separate what changed from why it changed in the description
- Keep the title specific, concise, and aligned with the actual implementation
- Include testing instructions that a reviewer can actually follow
- Never fabricate behavior — only describe what the code does
- Apply via
gh pr edit --title --body— do not just print the title or description
Output Format
Title and description applied to the GitHub PR via gh pr edit --title --body. Body sections should follow the repository PR template.
Reference Files
references/pr-description-template.md— PR body structure with checklist, summary, changes, testing, links, screenshots, and notes
Load references on demand via read_skill_file("git-pr", "references/{file}").
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026