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/dev-linkify-cc-resources
development
VerifiedTrustedCommunity
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
10SKILL.mdUpdated Jun 2, 2026
takazudo/opus-2nd
development
VerifiedTrustedCommunity
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd / /gcoc-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
10SKILL.mdUpdated May 29, 2026
takazudo/dev-ai-based-test
tools
VerifiedTrustedCommunity
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
10SKILL.mdUpdated May 29, 2026
takazudo/cleanup-resources
development
VerifiedTrustedCommunity
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.
10SKILL.mdUpdated May 29, 2026