takazudo/pr-make-suggestion-to-pr
skills/pr-make-suggestion-to-pr/SKILL.md
Create separate suggestion PRs from unstaged edits, each based on the current PR branch. Use when: (1) User says 'suggestion to pr' or 'create suggestion PRs', (2) After /pr-make-suggestion-edit has left unstaged changes that need to be turned into separate PRs by topic.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources pr-make-suggestion-to-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 8, 2026, 4:31 AM149.6s1 file scanned
SKILL.md
- name:
- pr-make-suggestion-to-pr
- description:
- Create separate suggestion PRs from unstaged edits, each based on the current PR branch. Use when: (1) User says 'suggestion to pr' or 'create suggestion PRs', (2) After /pr-make-suggestion-edit has left unstaged changes that need to be turned into separate PRs by topic.
PR Make Suggestion To PR
Create separate pull requests for each suggestion topic from the unstaged changes, with each PR based on the current PR branch.
Context
This command is typically used after /pr-make-suggestion-edit which leaves unstaged changes. These changes represent suggestions to improve the current PR, grouped by topic.
Process
Step 1: Analyze Unstaged Changes
- Check current branch and PR
- View all unstaged changes:
git status,git diff --stat,git diff - Analyze the changes and determine logical groupings
Step 2: Group Changes by Topic
Examples of topics:
- Formatting errors
- Type safety improvements
- Refactoring for better patterns
- Performance optimizations
- Accessibility improvements
Present the groupings to the user for confirmation.
Step 3: Create Suggestion PRs
For each topic, create a separate PR:
-
Create a new branch based on CURRENT branch (not base branch)
git checkout -b suggest/[descriptive-topic-name] $ORIGINAL_BRANCH -
Selectively stage only files for this topic
-
Create commit following project conventions
git commit -m "suggest: [clear description]" -
Push and create PR targeting the original PR branch
gh pr create --base $ORIGINAL_BRANCH --title "suggest: [title]" -
Return to original branch for next topic
Step 4: Verify and Report
List all created PRs and remaining unstaged changes.
Important Rules
Branch Strategy
- Base suggestion PRs on the CURRENT PR branch (not on main/master)
- Branch names should start with
suggest/ - This creates a chain: main <- original-pr <- suggestion-pr
Commit & PR Conventions
- PR titles MUST start with
suggest: - Follow project's commit message format
- Follow project's PR format
Process
- One topic = One PR (don't mix unrelated changes)
- Stage only relevant files for each PR
- Test that changes still work (type check if applicable)
- Provide clear URLs to all created PRs
Notes
- This command works with
/pr-make-suggestion-editas a pair - Each suggestion PR is independent and reviewable
- The base PR maintainer can choose which suggestions to merge
- After merging suggestions, they become part of the base PR
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