Loading...
Loading...
Found 471 Skills
A comprehensive Git command assistant and workflow guide. Trigger whenever the user asks how to perform a specific Git operation, wants to know what a Git command does, needs help fixing a Git mistake, or wants guidance on Git best practices (like branching, rebasing, or squashing).
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps. Use when the user asks to open or prepare a PR.
Generates structured changelogs and release notes from git history and PR descriptions. Classifies changes into breaking, features, fixes, performance, and docs. Filters internal-only changes, detects breaking changes, and produces human-readable entries linked to source PRs. Triggers on: "generate changelog", "write release notes", "compose changelog", "what changed since", "changes since last release", "prepare release", "release notes for", "changelog for", "summarize changes", "diff since tag". Use this skill when preparing a release and needing to summarize changes for users.
Review recent repository changes and decide whether AGENTS.md or other project-level documentation needs a high-level update. Use when finishing a feature, fix, refactor, or architectural change and you need to preserve repo-shaping guidance such as new patterns, constraints, workflows, validation rules, or onboarding-relevant gotchas without adding low-level implementation detail.
Use when needing multiple checked-out branches simultaneously without re-cloning — review a PR while keeping WIP, per-branch build caches, or hotfix alongside feature work
Stage and commit the intended changes with a clear message.
Ship a change via a feature branch and pull request — never directly to the default branch. Use after any code change, fix, refactor, or docs update that needs to land on main. Branches are named `<card-number>` from the FluentBoards card. Commits go through the husky pre-commit hook (lint-staged); pushes go to the feature branch only; the PR body links back to the card. Hard refuses any push to main / master / trunk.
Carefully integrate one Git branch into another without blindly accepting a mechanical merge or losing source-branch intent. Use when manually merging, transplanting, or refactoring branch work; when the user says not to blindly merge; when resolving conflicts while preserving clean current-branch structure; or when auditing that source additions, removals, tests, and docs all landed intentionally.
Archive completed changes and merge specification differences into permanent documents. Used when changes have been deployed, are ready for archiving, or when specifications need to be updated after implementation. Trigger words include "openspec archive", "archive", "archive proposal", "merge specifications", "complete proposal", "update documents", "finalize specifications", "mark as completed".
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
Creates GitHub pull requests with properly formatted titles. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request. Analyzes changes on the current branch and uses the pull request template from .github folder.
Unified git workflow for branch-first development: status/diff review, security-first commits, worktrees, and PR creation/review via gh. Auto-activates on: "commit", "push", "branch", "worktree", "pr", "pull request", "merge", "rebase", "git".