Git 與版本控制
6462 skills in 工具 > Git 與版本控制
github-pr-review-operation
GitHub Pull Requestのレビュー操作を行うスキル。PR情報取得、差分確認、コメント取得・投稿、インラインコメント、コメント返信をghコマンドで実行する。PRレビュー、コードレビュー、PR操作が必要な時に使用。
pr-author-agent
AI-powered PR Author Agent that transforms Observability Diff Plans into Pull Requests. Use when: (1) Generating instrumentation code from Scout Agent output, (2) Creating OTel configuration, correlation headers, lineage specs, (3) Scaffolding telemetry validation tests, (4) Creating GitHub/GitLab PRs with observability artifacts. Triggers: "generate PR from diff plan", "create instrumentation PR", "scaffold observability code", "generate OTel config".
premium-saas-ui
Build premium SaaS interfaces that avoid vibe-coded anti-patterns. Use when creating UI components, forms, dashboards, hero sections, pricing pages, or any user-facing templates. Enforces consistent spacing, typography, color discipline, and accessibility standards.
docs-and-changelogs
Generates comprehensive changelogs from Conventional Commits, maintains CHANGELOG.md files, and scaffolds project documentation like PRD.md or ADR.md. This skill should be used when creating changelogs, generating release notes, maintaining version history, documenting architectural decisions, or scaffolding project requirements documentation. Use for changelog generation, release notes, version documentation, ADR, PRD, or technical documentation.
am-i-a-tiger
For individual contributors who suspect they're carrying more organizational weight than their job title suggests.Analyzes your actual contribution patterns across git, Slack, and issue trackers to reveal if you're a "tiger" -one of those key people who actually keeps things running when something breaks.Use when you want to understand your real organizational impact, prepare for performance reviews,or figure out if you're being undervalued.Keywords: am I important, my contributions, invisible work, undervalued, tiger team, performance review,impact assessment, what do I actually do, recognition, career growth
a11y
Production-grade accessibility skill for WCAG 2.2 AA compliance.Covers auditing, remediation, component authoring, and validation workflows.Auto-invoked for UI implementation, a11y fixes, and accessibility testing.
a11y-checker-ci
Adds comprehensive accessibility testing to CI/CD pipelines using axe-core Playwright integration or pa11y-ci. Automatically generates markdown reports for pull requests showing WCAG violations with severity levels, affected elements, and remediation guidance. This skill should be used when implementing accessibility CI checks, adding a11y tests to pipelines, generating accessibility reports, enforcing WCAG compliance, automating accessibility scans, or setting up PR accessibility gates. Trigger terms include a11y ci, accessibility pipeline, wcag ci, axe-core ci, pa11y ci, accessibility reports, a11y automation, accessibility gate, compliance check.
cloudflare-observability-logging-monitoring
Use this skill whenever the user wants to improve or set up logging, tracing, metrics, and monitoring for Cloudflare Workers/Pages (e.g. Hono + TypeScript), including Wrangler tail, Workers Analytics, log structure, and integration with external tools like Sentry.
db-content
Database insertion via Prisma for MenFem content. Use when inserting articles, companies, culture picks, events, product reviews, explore features, or exchange listings into the database through conversational propose-approve-insert workflow. Trigger phrases include "insert article", "add to database", "create in prisma", "seed the database", or "populate the site".
sync-feature-branch
Commit current work to feature branch with Beads metadata tracking and git integration. MUST BE USED for all commit operations.Handles Feature-Key trailers, Beads status updates, and optional quick linting before commit.Use when user wants to save progress, commit changes, prepare work for review, sync local changes, or finalize current work,or when user mentions "uncommitted changes", "git status shows changes", "Feature-Key missing",commit operations, saving work, git workflows, or syncing changes.
gitagent
Use this skill in the scenario of writing git commit messages.
clean-branches
Clean up git branches by analyzing merged/unmerged status, archiving completed work,and organizing active branches. This skill should be used when the user wants to cleanup branches, organize their git repository, or review branch status.Triggered by "/clean-branches", "/branches", "clean branches", "check branches", "check branch", or "branches".
smukfest-sync
Synkronisering med Smukfest API for kunstnere og program. Brug ved dataopdatering, import af kunstnere, API-fejl, eller når du arbejder med sync scripts.
wt-cleanup
Identify and remove merged or stale git worktrees. Use for housekeeping, removes worktrees for branches that have been merged to main. Frees disk space.
deployment-workflow
Use this before committing code or when preparing for deployment. Provides pre-deployment checks, version bumping strategy, releases.json update pattern, common build failures, and deployment best practices.
issue-workflow
Issue-driven development workflow using GitHub issues as the source of truth. Use when asking "what's next?", checking project status, updating progress, or managing work priorities.
gitea
Interact with Gitea (self-hosted Git service) using the Gitea API. Use when working with Gitea repositories, issues, pull requests, or API operations.
skill-creator
Use this skill to create new Agent Skills for GitHub Copilot. It guides you through the process of setting up the directory structure and the SKILL.md file.
markdown-formatter
Format and lint Markdown documents with consistent style, proper heading hierarchy, link validation, and code block formatting. Use when working with Markdown files, documentation, README files, or technical writing. Checks for common issues like broken links, inconsistent formatting, and missing alt text. Triggers on "format markdown", "lint markdown", "markdown style", ".md file", "documentation formatting".
spec-management
Templates, scripts, and examples for managing feature specifications in specs/ directory. Use when creating feature specs, listing specifications, validating spec completeness, updating spec status, searching spec content, organizing project requirements, tracking feature development, managing technical documentation, or when user mentions spec management, feature specifications, requirements docs, spec validation, or specification organization.