ilya-valasiuk/creating-pull-requests
skills/creating-pull-requests/SKILL.md
Prepare and open pull requests using the team's PR template, including a short PR title, diff-based classification into Features and Fixes, and an approval checkpoint before any push or PR creation. Use when the user asks to create, draft, preview, or open a pull request.
testing
Updated May 30, 2026
$ install --global
skillsauthnpx skillsauth add ilya-valasiuk/agent-skills creating-pull-requestsInstall 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 30, 2026, 2:37 AM154.4s4 files scanned
SKILL.md
- name:
- creating-pull-requests
- description:
- Prepare and open pull requests using the team's PR template, including a short PR title, diff-based classification into Features and Fixes, and an approval checkpoint before any push or PR creation. Use when the user asks to create, draft, preview, or open a pull request.
- license:
- MIT
- allowed-tools:
- Bash
Creating Pull Requests
Prepare a PR from the current branch, show a preview, and open it only after explicit approval.
Rules
- Inspect the real branch changes before drafting the PR.
- Always show the title and body preview before pushing or opening the PR.
- Never push or create a PR without explicit approval.
- If
FeaturesorFixeshas no real items, writeN/A. - For release PRs targeting
main, always use the titleRelease.
Workflow
Copy this checklist and track progress:
PR Progress:
- [ ] Step 1: Inspect branch and choose base
- [ ] Step 2: Identify main story and work items
- [ ] Step 3: Classify items into Features and Fixes
- [ ] Step 4: Draft title and PR body
- [ ] Step 5: Show preview and wait for approval
- [ ] Step 6: Push and open PR, or provide fallback handoff
Step 1: Inspect branch and choose base
Check branch name, status, commits, and diff against the target branch.
Default base: origin/develop
Use another base when:
- the user explicitly names it
- the repo flow clearly uses another target
- this is a release PR to
main
If the correct base is unclear, ask before finalizing.
Common commands:
git branch --show-current
git status --short
git log --oneline --decorate -n 15
git diff --stat origin/develop...HEAD
git diff origin/develop...HEAD
Step 2: Identify the branch story
Summarize what the branch mainly does.
Prefer task names and work item links from:
- user context
- branch names
- commit messages
- issue or board references
Step 3: Classify items
Use behavior, not filenames.
Features: new or expanded capabilityFixes: corrected broken behavior, regression, or edge case
Do not force refactors or maintenance work into either section unless they are the only changes worth mentioning for reviewer context.
Classification and bullet patterns: see references/REFERENCE.md
Step 4: Draft title and body
Title priority:
- task or work item name, if it clearly matches the branch
- main outcome inferred from the diff
- concise synthesized title
Prefer short natural-language titles focused on the main outcome.
Build the PR body using the exact team template from references/TEMPLATES.md.
Step 5: Show preview and wait
Before any push or PR creation, show:
- proposed PR title
- proposed PR body
- target base branch when useful
Use the preview template from references/TEMPLATES.md, then stop and wait for approval.
Step 6: Push and open PR, or provide fallback handoff
After approval:
- push the branch if needed
- create the PR with the approved title and body
If GitHub CLI is available, prefer gh pr create.
If PR creation succeeds, use the success response template from references/TEMPLATES.md.
If automatic PR creation is blocked because of missing CLI, invalid auth, sandbox/network restrictions, or unavailable repo tooling, do not stop with an error. Use the fallback response template from references/TEMPLATES.md, and build the compare link using the GitHub format documented in references/REFERENCE.md.
References
- references/REFERENCE.md: classification rules, title guidance, command guidance
- references/TEMPLATES.md: team PR body template, preview template, success template, fallback template
- references/EXAMPLES.md: example scenarios
Related Skills
ilya-valasiuk/structuring-nextjs-app-router
tools
VerifiedTrustedCommunity
Standardize and preserve Next.js App Router project structure across `src/`, including route files, page composition, API modules, server actions, hooks, providers, helpers, and shared utilities. Use this skill whenever the user asks to add, move, rename, refactor, or review files in a Next.js App Router codebase, especially if the task affects file placement, page architecture, or folder naming.
SKILL.mdUpdated May 30, 2026
ilya-valasiuk/organizing-classnames
development
VerifiedTrustedCommunity
Enforces classNames package usage patterns and Tailwind CSS class ordering conventions in React components. Use this skill whenever writing or reviewing component className props, applying Tailwind classes, using the classnames package, organizing breakpoint-specific styles, writing conditional class expressions, or when the user asks about CSS class ordering, mobile-first responsive patterns, or how to handle className props in components.
SKILL.mdUpdated May 22, 2026
ilya-valasiuk/generating-typeorm-migration
testing
VerifiedTrustedCommunity
Explains how to create and review TypeORM migrations. Use this skill whenever the user wants to change an entity, add or update schema-related database objects, generate a migration, or decide whether a database change should be handled through TypeORM metadata or a custom migration.
SKILL.mdUpdated May 22, 2026
ilya-valasiuk/building-components
development
VerifiedTrustedCommunity
Builds, restructures, and standardizes React components according to project conventions (placement, folder/file naming, exports, props patterns). Use when adding components or when reorganizing existing components during refactors, migrations, or component moves.
SKILL.mdUpdated May 22, 2026