git-workflows
1
pr-creation
Use when creating pull requests to auto-generate PR descriptions from plan, execution context, and memory - handles pre-flight checks, description generation, and GitHub CLI integration
seanGSISG
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
git-workflows
1
repo-readiness
Prepare any repository for new work by analyzing CLAUDE.md, file structure, mission/objectives, and establishing work readiness state. Auto-executes before new tasks to provide context.
vamseeachanta
devops
git-workflows
0
tech-debt-tracker
Track, prioritize, and pay down technical debt systematically in ANY project. Use when quantifying debt, prioritizing fixes, or convincing management to invest in improvements.
j0KZ
devops
git-workflows
0
sparc-planning
Creates comprehensive implementation plans using the SPARC framework (Specification, Pseudocode, Architecture, Refinement, Completion). Automatically invokes check-history for context, generates detailed plans with ranked task lists, dependency graphs, security/performance considerations. For significant features (>8 hours), major refactoring, breaking changes, or multi-component work.
meriley
devops
git-workflows
0
tech-debt-tracker
Track, prioritize, and pay down technical debt systematically in ANY project
j0KZ
devops
git-workflows
0
tech-debt-tracker
Track, prioritize, and pay down technical debt systematically in ANY project
j0KZ
devops
git-workflows
0
milestone-delivery-path-reanalysis
Keeps GitHub milestone descriptions in sync with milestone issue CRUD by reanalyzing delivery slices, inserting gaps, and applying a deterministic ordered plan (with auth + heredoc guardrails). This should be used when there is a change to a milestone or a substantial change to an issue in a milestone.
piquet-h
devops
git-workflows
0
understand-code
Primer on how to best visualise a repo/feature in a codebase
OscarAdserballe
devops
git-workflows
0
global-conventions
Follow development best practices including consistent project structure, clear documentation with README files, version control best practices with clear commit messages, environment configuration using environment variables, minimal dependency management, code review processes, testing requirements, feature flags for incomplete features, and changelog maintenance. Use this skill when organizing project files and directories, writing commit messages, managing dependencies, setting up environment configurations, establishing code review processes, or maintaining project documentation. This skill applies when working on project organization, git workflows, dependency management, or any project-level conventions.
FlorianRiquelme
devops
git-workflows
0
landing-the-plane
Checklist for finishing work, pushing a branch, and opening a ready-for-review PR with tests and tracker updates. Use when asked to "land the plane"
Ramblurr
devops
git-workflows
0
incremental-development
Structured incremental development workflow that enforces explicit scoping before implementation. Use when: (1) User says 'build', 'implement', 'develop', 'create feature', or 'add functionality', (2) Task involves multiple files or could have ripple effects, (3) User wants to avoid scope creep or premature implementation, (4) Breaking down complex tasks into verifiable steps. This skill prevents AI agents from jumping into code without a validated plan.
even-wei
devops
git-workflows
0
krammestructured-implementation-workflow
Use a structured workflow with three interconnected documents (main specification, open issues, and log) to plan, track, and document complex implementations, ensuring clarity and continuity. Use when you detect the presence of LOG.md and OPEN_ISSUES.md files.
Abildtoft
devops
git-workflows
0
branch-management
main, develop, release ブランチに関するPR作成、マージ、ブランチ作成時にブランチ戦略を確認・案内する
tettuan
devops
git-workflows
0
spec-driven-development
Spec-Driven Development workflow using GitHub spec-kit for building high-quality software with structured specifications and intent-driven development
vineethsoma
devops
git-workflows
0
beads-issue-tracking
Track complex, multi-session work with dependency graphs using beads (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
shaneholloman
devops
git-workflows
0
git-workflow
Especialista em Git, estratégias de branching, resolução de conflitos e workflows colaborativos
automacoescomerciaisintegradas
devops
git-workflows
0
github-issue
gh CLIでGitHub Issueを作成するスキル。現在の動作/期待する動作/再現手順/環境情報などの最小入力から、AIが作業可能な構造化Issue（調査・修正・検証の手順と受け入れ条件付き）を作成する。Codex/Claude/Gemini/Cursorで共通化したIssue作成を行うときに使用する。
RECERQA
devops
git-workflows
0
github-actions-logs
GitHub Actions 워크플로우 로그를 조회하고 분석합니다. "CI 로그 확인해줘", "워크플로우 실패 원인 분석해줘", "GitHub Actions 상태 알려줘", "빌드 로그 보여줘", "테스트 실패 로그 확인" 등을 요청할 때 활성화됩니다.
dlddu
devops
git-workflows
0
board-status
Check GitHub Project board status for the monorepo. Use when user asks about board status, what's in progress, sprint status, or issue tracking.
rollercoaster-dev
devops
git-workflows
0
flight-prime
Prime context for a task - research, scan codebase, gather domain constraints. Use when starting implementation of a task file, PRD, or clear task description.
mojoatomic
devops
git-workflows
0
global-conventions
Follow truth-first development with focused feature work, accurate spec maintenance, clean version control, environment-based configuration, and infrastructure-as-code deployments. Use this skill when managing requirements, working in branches, handling configuration, reviewing code, maintaining documentation, or deploying with Ansible. Applies to all development activities requiring honest communication, systematic processes, dependency management, and radical transparency in documentation and decision logs.
grimmolf
devops
git-workflows
0
forensic-knowledge-mapping
Use when assessing team resilience, planning for developer departures, calculating bus/truck factor, identifying knowledge silos, or evaluating organizational risk - maps code ownership from git history and identifies single points of failure using research-backed thresholds (>80% ownership = silo)
AlabamaMike
devops