takazudo/pr-revise
skills/pr-revise/SKILL.md
Update an existing PR's title and description to reflect the full implementation. Use when: (1) User says 'revise pr', 'update pr description', 'pr revise', (2) Additional work was done after the PR was created and the title/body no longer matches, (3) User wants to sync PR metadata with the branch state.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources pr-reviseInstall 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: Jul 2, 2026, 5:08 AM112.5s1 file scanned
SKILL.md
- name:
- pr-revise
- description:
- Update an existing PR's title and description to reflect the full implementation. Use when: (1) User says 'revise pr', 'update pr description', 'pr revise', (2) Additional work was done after the PR was created and the title/body no longer matches, (3) User wants to sync PR metadata with the branch state.
PR Revise
Update an existing PR's title and description to accurately reflect the full implementation, not just the original scope.
Prerequisites
- Current branch must have an open PR
- If no PR is found, abort with a message: "No PR found for the current branch."
Step 1: Gather PR and Branch Context
# Get current branch
BRANCH=$(git branch --show-current)
# Fetch latest
git fetch origin
# Get PR details
gh pr view "$BRANCH" --json number,title,body,baseRefName,headRefName
Record the PR number, current title, current body, and base branch.
Step 2: Analyze Full Implementation
Review ALL changes in the PR — not just recent commits:
BASE_BRANCH=<baseRefName from step 1>
# All commits in the PR
git log "origin/$BASE_BRANCH".."$BRANCH" --oneline
# Full diff stat
git diff "origin/$BASE_BRANCH"..."$BRANCH" --stat
# Full diff for understanding
git diff "origin/$BASE_BRANCH"..."$BRANCH"
Read the diff carefully. Understand:
- What features were added
- What was refactored or fixed
- What files were created, modified, or deleted
- The overall scope and purpose of the changes
Step 3: Draft New Title and Description
Based on the full diff analysis:
Title: Write a concise PR title (under 70 chars) that captures the overall scope. If the PR covers multiple concerns, summarize the primary theme.
Description: Write a comprehensive PR body using this format:
## Summary
<2-4 bullet points covering the main changes>
## Changes
<Detailed list of what was done, grouped by category if needed>
## Test Plan
<How to verify the changes work correctly>
If the original body contained issue references (e.g., Closes #123, Fixes #456), preserve them in the new body.
Step 4: Show the User What Will Change
Present the proposed updates clearly:
Current title: <old title>
New title: <new title>
Current body:
<old body>
New body:
<new body>
Ask the user to confirm before applying.
Step 5: Apply Updates
PR_NUMBER=<number from step 1>
# Update title
gh pr edit "$PR_NUMBER" --title "<new title>"
# Update body
gh pr edit "$PR_NUMBER" --body "$(cat <<'EOF'
<new body content>
EOF
)"
Report the updated PR URL when done.
Important Notes
- Always analyze the FULL diff against the base branch, not just recent commits
- Preserve issue references from the original body
- Do not change the PR's base branch or draft status
- If the diff is very large, use
--statfirst to get an overview, then read key files selectively
Related Skills
takazudo/finalize-codex-work
tools
VerifiedTrustedCommunity
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
11SKILL.mdUpdated Jul 10, 2026
takazudo/fig-url-refer
tools
VerifiedTrustedCommunity
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
11SKILL.mdUpdated Jul 10, 2026
takazudo/dev-codex-sync-settings-from-claude
tools
VerifiedTrustedCommunity
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
11SKILL.mdUpdated Jul 10, 2026
takazudo/video-reader
development
VerifiedTrustedCommunity
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.
11SKILL.mdUpdated Jul 7, 2026