Loading...
Loading...
Found 409 Skills
Git Commit Rules
Perforce shelving for code review, sharing work-in-progress, backup, and collaboration workflows.
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Create a git commit following project conventions
GitLab repository operations. ALWAYS use this skill when user wants to: (1) clone repositories, (2) fork projects, (3) view repo info, (4) create new projects, (5) archive/delete repos, (6) manage repo settings.
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.
The human project owner and final authority. Does not write code or run tools -- resolves tie-breaks, approves or denies major decisions, and unblocks deadlocks.
Generate GitHub Pull Request title and description from branch changes
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.