Loading...
Loading...
Found 319 Skills
Create a git commit following project conventions
Analyze, plan, and execute FireCrawl SDK upgrades with breaking change detection. Use when upgrading FireCrawl SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade firecrawl", "firecrawl migration", "firecrawl breaking changes", "update firecrawl SDK", "analyze firecrawl version".
Read this skill before creating any git commit to ensure the commit message matches the project's established patterns. Triggers on: git commit, /commit, creating commits, or any task that results in a git commit.
Split changes into a Graphite stack with PR titles and descriptions. Use when asked to create or propose a stacked PR series.
Git commit message best practices. Use when writing commit messages, reviewing commits, or setting up commit conventions for a project. Ensures clear, consistent, and useful commit history.
Create or update a GitHub pull request with a Japanese title and body, using .github/pull_request_template.md or docs/pull_request_template.md when present. Use when the user asks to open a PR, create a pull request, or refresh PR metadata. Requires a pushed branch—use push (and pull if needed) first; use commit-jp for commits.
Commit unstaged changes, push changes, submit a pull request.
Commit, push, and open a pull request in Azure DevOps. Use whenever the user wants to open, update, or draft a PR and the project is hosted on Azure DevOps (`dev.azure.com`, `visualstudio.com`, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`). Links work items to the PR, sets reviewers, and supports draft-by-default.
Follow up on an existing PR by rebasing on the base branch, addressing reviewer comments, fixing CI issues, and pushing updates. Use when the user provides a PR URL or number and wants to get it ready for merge.
git, git tags, pushing and pulling to repository. Any version control tasks.
Conventional Commits 1.0.0 + 베스트 프랙티스 워크플로 (diff → staging → type 결정 → secrets blocklist → 사전 체크리스트) + 5 founding principle (atomic / leaves-repo-green / why-over-what / imperative / searchable) + project dialect scaffolding. 커밋을 4 reader (`git log` 스캐너 / `git blame` 추적자 / `git bisect` 사냥꾼 / AI agent — `/clear` 컨텍스트 복원 / PR 리뷰 / changelog 생성 / NL 질의)에게 동시에 도움되는 영구 history로 다룸. 본 파일은 한국어 prose 변형. 룰 자체 (영문 default body, lowercase summary, imperative mood, atomic / why-over-what 등 §0 전 원칙)는 영문 SKILL.md와 동일 — 변형 무관. ALWAYS trigger 조건은 영문 SKILL.md frontmatter §ALWAYS와 동일. Triggers (multi-lingual): EN: commit, git commit, stage, commit message, breaking change, conventional commits, revert, fixup, amend, cherry-pick, changelog KO: 커밋, 깃 커밋, 스테이지, 커밋 메시지, 커밋 룰, 컨벤셔널 커밋, 리버트, 되돌리기, 어맨드, 커밋 컨벤션, 커밋 메시지 검토 JA: コミット, git コミット, ステージ, コミットメッセージ, ブレーキング チェンジ, リバート, アメンド ZH: 提交, git 提交, 暂存, 提交信息, 提交消息, 重大变更, 回滚, 修订 Audience: 한국어를 모국어로 쓰는 개발자. §0 founding principle을 한국어로 먼저 잡고 싶은 사용자에게 적합. §1-§14 룰 자체는 영문 SKILL.md를 정본으로 참조 — 본 변형이 룰을 새로 정의하지 않음.
Organize design assets, optimize images and fonts, maintain brand asset libraries, implement version control for assets, and enforce naming conventions. Use when optimizing images for web, converting fonts to WOFF2, organizing asset directories, setting up responsive image pipelines, or managing logo variants.