菜单
Use this skill when the user wants to write a git commit message, create a PR (pull request), design a branch naming strategy, write a PR description, or follow Git workflow conventions. Use when the user mentions commit, PR, branch, merge, rebase, or git conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
This skill should be loaded for any task involving web application security. Use it when building or reviewing HTTP/HTTPS endpoints, REST APIs, GraphQL APIs, WebSocket services, SPAs, or any server-side code that processes untrusted user input. Also load it for security audits, penetration testing guidance, secure code review, or vulnerability assessments. Triggers on: "security check", "vuln", "injection", "XSS", "CSRF", "auth", "session", "pentest", "OWASP", "CVE", "secure coding", "취약점", "웹 보안", "보안 점검", "시큐어코딩". When in doubt, load it.
Use this skill when the user wants to build, integrate with, or send messages to Discord. Covers Discord bots using discord.js (Node.js) or discord.py (Python), direct REST API calls, and webhook integrations. Use when the user mentions Discord bots, slash commands, events, webhooks, embeds, channels, sending messages to Discord, mention injection (@everyone abuse), or markdown security.
基于 SOC 职业分类
| name | git-workflow |
| description | Use this skill when the user wants to write a git commit message, create a PR (pull request), design a branch naming strategy, write a PR description, or follow Git workflow conventions. Use when the user mentions commit, PR, branch, merge, rebase, or git conventions. |
Enforce consistent conventions for commit messages, branch naming, and pull request descriptions.
Read: references/commit-convention.md
Format:
<type>(<scope>): <subject>
[optional body]
[optional footer]
Core Rules:
type must be chosen from the list belowsubject is imperative mood, lowercase, no trailing periodType List:
| type | When to use |
|---|---|
feat | A new feature |
fix | A bug fix |
docs | Documentation changes only |
style | Formatting, no logic change |
refactor | Code restructure, no behavior change |
test | Adding or updating tests |
chore | Build, dependencies, config changes |
perf | Performance improvement |
ci | CI/CD configuration changes |
revert | Reverting a previous commit |
Examples:
feat(auth): add OAuth2 login with Google
fix(api): handle null response from Discord webhook
docs(readme): add skill installation guide
chore(deps): upgrade discord.js to v14.16
Validate a commit message with the script:
bash scripts/validate_commit.sh "feat(auth): add login"
Read: references/branching-strategy.md
Branch Naming Convention:
<type>/<issue-number>-<short-description>
Examples:
feat/42-oauth-login
fix/87-webhook-null-error
docs/12-update-readme
refactor/55-auth-module
Branch Structure (GitHub Flow):
main ← always deployable
└─ feat/... ← feature development
└─ fix/... ← bug fixes
└─ docs/... ← documentation
For complex projects, consider adding a
developbranch (Git Flow). Read:references/branching-strategy.md→ "Git Flow" section
Validate a branch name with the script:
bash scripts/validate_branch.sh "feat/42-oauth-login"
Read: references/pr-template.md
Use the template at resources/PR_TEMPLATE.md when writing a PR.
Key Sections:
PR Checklist:
subject line of a commit message under 72 charactersmainWIP: commits before merging