rstackjs/pr-creator
skills/pr-creator/SKILL.md
Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.
$ install --global
skillsauthnpx skillsauth add rstackjs/agent-skills pr-creatorInstall 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: Apr 30, 2026, 5:10 AM9.5s1 file scanned
SKILL.md
- name:
- pr-creator
- description:
- Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.
Pull Request Creator
Steps
-
Confirm the current branch with
git branch --show-current. If it is the default branch, create and switch to a new branch before doing anything else. Use a descriptive branch name, preferablyfeat-<topic>orfix-<topic>. -
Review local changes with
git status --short. Do not revert unrelated user changes. Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch. -
If
.github/PULL_REQUEST_TEMPLATE.mdexists, read it and follow its structure. -
Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
feat(core): add ...fix(types): ...docs: ...refactor(types): ...chore(deps): ...release: v1.2.0
-
Write the PR body in concise, clear English.
- In
Summary, explain the change context first: the user-facing problem, maintenance goal, or compatibility constraint that makes the change necessary. - Prioritize high-signal information: public API changes, behavior changes, breaking changes, migration notes, and important compatibility implications.
- Then describe the main implementation change only as much as needed to understand the review.
- Keep it short: one compact paragraph or 2-4 bullets is usually enough.
- Avoid low-signal sections such as
Test planorValidation, routine verification commands, generated file lists, or obvious implementation details unless the repository template explicitly requires them or the change has unusual validation risk. - Good background examples:
This PR adds support for custom logger injection so CLI output can be isolated per instance.This PR fixes incorrect padding in URL labels to keep terminal output aligned across different label lengths.This PR updates the English docs to clarify how the extraction option works and when to enable it.
- In
-
Fill
Related Linkswith issue links, design docs, related PRs, or discussion pages. If the PR upgrades an npm dependency, add a link to the upgraded version's release notes or tag page when available. Example:https://github.com/web-infra-dev/rspack/releases/tag/v1.0.0If there is no relevant link, omit the entireRelated Linkssection from the PR body. -
Push the branch only after re-checking the branch name. Never push the default branch directly.
-
Create the PR with
gh pr create.
Constraints
- Do not modify code while following this skill.
Related Skills
rstackjs/rstest-debugging
development
VerifiedTrustedCommunity
Debug Rstest issues systematically, including performance regressions. First determine whether the slowdown is in build startup or test execution, then run controlled config or code experiments and compare before/after timings.
68SKILL.mdUpdated May 21, 2026
rstackjs/rslib-modern-package
development
VerifiedTrustedCommunity
Opinionated Rslib recommendations for modern JS/TS npm package design covering pure ESM, strict TypeScript, explicit exports, small stable APIs, pragmatic dependencies, accurate sideEffects, correct declarations, package validation, provenance, README.md, and AGENTS.md. Use when the user wants to make a JS/TS package more modern, check whether the current package setup is healthy, review package.json/exports/types/dependencies/docs/release readiness, or apply a modern library baseline.
68SKILL.mdUpdated May 21, 2026
rstackjs/create-draft-release-notes
development
VerifiedTrustedCommunity
Create or update draft GitHub releases for the current project's main GitHub repository, then organize GitHub-generated release notes into user-friendly sections without rewriting release note items. Use for preparing, formatting, categorizing, creating, or updating GitHub release notes or draft releases, including optional highlights when the user asks for them.
68SKILL.mdUpdated May 21, 2026
rstackjs/migrate-to-rslint
tools
VerifiedTrustedCommunity
Migrate ESLint or other linters to Rslint. Use when asked to replace ESLint flat config, lint scripts, VS Code ESLint settings, inline directives, rules, presets, plugins, or lint dependencies with Rslint equivalents.
68SKILL.mdUpdated May 10, 2026