cicd
0
plan-reviewer
Review a development plan before implementation to identify risks, missing considerations, and better alternatives. Use for plans involving auth changes, migrations, integrations, or other high-impact work.
ogprotege
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
cloud
0
cost-optimization
Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
HermeticOrmus
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
cicd
0
faion-feature-executor
SDD feature executor: sequential task execution with quality gates. Runs tests/coverage validation after each task, performs code review, iterates until all issues resolved. Integrates with faion-task-executor-agent.
faionfaion
devops
cicd
0
tool-roadmap-planner
Create phased implementation roadmaps for development tools, breaking them into MVP, enhancements, and polish phases with feature-level deliverables compatible with tool-feature-implementer.
cautiouskurns
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
cicd
0
aico-subagent-driven
Execute implementation plan by dispatching fresh subagent per task. Each task gets: Implementer → Spec Review → Quality Review. Two-stage review ensures both correctness and quality. Use this skill when: - Have implementation plan with multiple independent tasks - Want automated execution with quality gates after each task - Tasks are mostly independent (not tightly coupled) - User asks to "execute the plan", "run the tasks", "auto implement" Prerequisites: Must have plan from aico-*-plan or aico-*-task-breakdown skill. Process: For each task: Dispatch Implementer → Spec Review (passes?) → Quality Review (passes?) → Next task Review order: ALWAYS spec compliance first, THEN code quality.
yellinzero
devops
cicd
0
whisper-lolo-roadmap
Guide development of the whisper-lolo project based on specifications-projet.md. Use when planning or executing a sprint/PR, validating scope or constraints, or aligning architecture, statuses, and DoD for the Next.js + Vercel + Blob + Inngest + Whisper stack.
Lofp34
devops
cicd
0
jam-prep-checklist
setup preparation readiness checklist pre-jam verification launch ready
karchtho
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
cicd
0
workbench-architecture
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
bravellian
devops
cicd
0
yux-ci-monitor
Monitor CI/CD status for pull requests with error reporting. Triggers: "check CI", "CI status", "workflow status", "monitor CI", "检查CI", "CI状态", "查看构建".
wuyuxiangX
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
cicd
0
multi-agent-coordinator
Spawn 10-20 parallel agents for Leavn codebase audits, systematic fixes, comprehensive analysis across multiple domains simultaneously
willsigmon
devops
monitoring
0
railway-observability
Railway.com built-in metrics, monitoring dashboards, alerting (Pro plan), and external OTEL integration with Grafana. Use when setting up monitoring, creating dashboards, configuring alerts, integrating Prometheus/Loki/Tempo, deploying Grafana stack, or analyzing Railway service metrics.
adaptationio
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
cicd
0
qa-gatekeeper-testing-cicd-pipeline
Quality assurance workflow for PR reviews, CI pipeline monitoring, and production verification
oviney
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