takazudo/pr-recreate
skills/pr-recreate/SKILL.md
Recreate a PR with clean commit history when it has too many messy commits. Use when: (1) User says 'recreate pr' or 'clean up pr history', (2) A PR has accumulated try-and-error commits and needs a fresh start, (3) User wants to squash messy history into clean logical commits.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources pr-recreateInstall 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 10, 2026, 5:49 AM130.2s1 file scanned
SKILL.md
- name:
- pr-recreate
- description:
- Recreate a PR with clean commit history when it has too many messy commits. Use when: (1) User says 'recreate pr' or 'clean up pr history', (2) A PR has accumulated try-and-error commits and needs a fresh start, (3) User wants to squash messy history into clean logical commits.
- argument-hint:
- [PR_URL]
PR Recreate Command
Recreate a PR with a clean history when it has too many try-and-error commits or review comments.
IMPORTANT: This command ALWAYS uses squash merge to discard try-and-error history and create clean, meaningful commits. Never use cherry-pick.
Usage
/pr-recreate- Recreate PR for current branch/pr-recreate <PR_URL>- Recreate PR from specified URL
Steps
1. Identify Target PR
- If PR URL provided: Extract PR information using
gh pr view <URL> - If no URL: Get current branch and find PR using
gh pr list --head <current-branch>
2. Analyze PR Information
Extract:
- Old branch name
- Base branch (CRITICAL: Extract from
gh pr view --json baseRefName) - PR title
- PR number
- Original issue reference
CRITICAL: ALWAYS use the exact base branch from the original PR - NEVER default to main or develop
3. Determine New Branch Name
Check for existing versioned branches and generate next available version:
implement-foo-bar->implement-foo-bar-v2(or-v3if-v2exists)
4. Create New Branch
git fetch origin
git checkout -b <new-branch> origin/<base-branch>
5. Squash Merge Old Branch
git merge --squash origin/<old-branch>
6. Create Meaningful Commits
CRITICAL: ALWAYS create MULTIPLE meaningful commits - NEVER just one commit
- Review staged changes with
git diff --cached - Break down into logical units (feature, tests, docs, refactoring)
- Create separate commits for each unit
- Aim for 2-5 commits minimum
CRITICAL - NO COMMIT ALTERATION:
- NEVER use
git commit --amend - NEVER use
git rebase - Each commit must be created fresh
7. Push New Branch
git push -u origin <new-branch>
8. Create New PR
Use the EXACT base branch from step 2. Include:
- Original issue reference FIRST
- PR description
- Old PR reference LAST
9. Update Old PR
- Add
[outdated]prefix to title - Add comment referencing new PR
- Close old PR
10. Report Summary
- Old PR: #<number> (closed)
- New PR: #<number> (created)
- Branch:
<old-branch>-><new-branch> - Commits created
- Base branch
Important Notes
- CRITICAL: ALWAYS use squash merge to discard try-and-error history
- CRITICAL: ALWAYS use the original PR's base branch
- CRITICAL: Never alter commits (no amend, no rebase, no force push)
- CRITICAL: Create MULTIPLE meaningful commits (2-5 minimum)
- If the target project's CLAUDE.md defines PR conventions (e.g. Japanese titles, an AI-attribution header in the PR body/comments), follow them — otherwise use clear defaults
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