liangmiQwQ/creating-pr
skills/creating-pr/SKILL.md
Load this skill before creating, drafting, modifying, or submitting PR on GitHub
tools
Updated Jun 6, 2026
$ install --global
skillsauthnpx skillsauth add liangmiQwQ/skills creating-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: Jun 6, 2026, 2:23 AM97.9s1 file scanned
SKILL.md
- name:
- creating-pr
- description:
- Load this skill before creating, drafting, modifying, or submitting PR on GitHub
Title
For most projects, maintainers use squash and merge. We should follow Conventional Commits for PR title.
<type>[optional scope]: <description>
The type of PR is decided on the code behavior changes. For example, even if a PR is linked to a Bug issue, but it actually adds the missing feature to close it, its type still should be feat.
We generally use a lowercase starting imperative sentence as the <description> part.
For example
feat(cli): add global packages support
PR Setting
If no special requirement provided, submit draft PR.
Always check Allow edits by maintainers.
Description
PR description should always follow simple and human-readable principles.
Avoid excessive headings and checklists when simple paragraphs are enough. Try to use short paragraphs to express your idea and implementation details. Try using sentences like This PR adds ..., The current behavior ..., Follows ...'s behavior, It means that, It doesn't mean that
If this PR is linked to an issue, put a Close #xyz on the top of the description.
For bug fixes without an issue, you should describe the bug first. And then describe this PR's changes.
For projects with .github/workflows, we do not need to describe Validation part because CI will help verify your implementation.
In order to make the pr description simple and easy to read, we should use simple words and simple sentences. Some well-known project specifications and everyday-chores may also be omitted. (For example, a snap test added in a fix pr, we do not need to mention this addition).
Add a line 🤖 Generated with [The Agent Tool's Name] in the bottom of the description.
A good PR description should like this, comments should be removed in practice. Paragraphs inside CORE DESCRIPTION part can be repeated or skipped as needed.
Close #1 <!-- If there is a linked issue -->
<!-- CORE DESCRIPTION START -->
The current ... <!-- Describe a bug or current behavior if no issue linked-->
This PR adds ... <!-- Describe behavior changes if there is -->
This PR includes ... <!-- Describe implement details if it is worth telling like refactor, module movements,especially for chore/refactor PR -->
No behavior changes. <!-- If this is a chore/refactor PR -->
<!-- CORE DESCRIPTION END -->
🤖 Generated with [Agent Name] <!-- Replace [Agent Name] with the tool you're using, e.g. Codex / Claude Code. -->
Related Skills
liangmiQwQ/cc-design
development
VerifiedTrustedCommunity
High-fidelity HTML design and prototype creation. Use this skill whenever the user asks to design, prototype, mock up, or build visual artifacts in HTML — including slide decks, interactive prototypes, landing pages, UI mockups, animations, or any visual design work. Also use when the user mentions Figma, design systems, UI kits, wireframes, presentations, or wants to explore visual design directions. Even if they just say "make it look good" or "design a screen for X", this skill applies.
SKILL.mdUpdated Jun 5, 2026
liangmiQwQ/cc-design
development
VerifiedTrustedCommunity
High-fidelity HTML design and prototype creation. Use this skill whenever the user asks to design, prototype, mock up, or build visual artifacts in HTML — including slide decks, interactive prototypes, landing pages, UI mockups, animations, or any visual design work. Also use when the user mentions Figma, design systems, UI kits, wireframes, presentations, or wants to explore visual design directions. Even if they just say "make it look good" or "design a screen for X", this skill applies.
SKILL.mdUpdated Jun 5, 2026
liangmiQwQ/global-projects
development
VerifiedTrustedCommunity
Load this skill when Codex needs to locate, enter, clone, open, or coordinate work across the user's local projects. Use it when the current directory is not the target project, when another local project is needed, or when multiple projects are involved. The user's standard is rootPath/github-owner/repo, managed by mo.
SKILL.mdUpdated Jun 1, 2026
liangmiQwQ/creating-pr
tools
VerifiedTrustedCommunity
Load this skill before creating, drafting, modifying, or submitting PR on GitHub
SKILL.mdUpdated May 24, 2026