GitHub
ui-ux-pro-max
UI/UX design intelligence with searchable database: 50 styles, 21 color palettes, 50 font pairings, 20 chart types, 8 framework stacks. Trigger phrases (use this skill when user says): - "build a landing page"...
Skills IA devops project management
Découvrez les skills devops project management, comparez leurs dépôts et consultez leurs instructions.
Catégories: devops project management
devops project management Effacer les filtres
Explorer
GitHub
mermaid
Guide for creating mermaid diagrams. This skill should be used when users want to create a mermaid diagram (or update an existing diagram).
GitHub
github-actions-logs
GitHub Actions 워크플로우 로그를 조회하고 분석합니다. "CI 로그 확인해줘", "워크플로우 실패 원인 분석해줘", "GitHub Actions 상태 알려줘", "빌드 로그 보여줘", "테스트 실패 로그 확인" 등을 요청할 때 활성화됩니다.
GitHub
implementation
작업 계획서를 기반으로 TDD 방식으로 구현합니다. "구현 시작", "코드 작성", "개발 진행", "TDD" 등의 요청 시 활성화됩니다.
GitHub
task-planning
인수 테스트를 기반으로 남은 작업을 분석하고 다음 작업을 계획합니다. "작업 계획", "다음 작업", "할 일 확인", "남은 작업" 등의 요청 시 활성화됩니다.
GitHub
project-bootstrap
요구사항 명세를 기반으로 프로젝트 구조와 CI 파이프라인을 설정합니다. "프로젝트 초기화해줘", "프로젝트 부트스트랩", "CI 설정해줘", "프로젝트 구조 만들어줘" 등을 요청할 때 활성화됩니다.
GitHub
task-planning
명세서와 사용자 스토리를 분석하여 다음 작업을 계획합니다. "다음 작업 뭐야", "작업 계획 세워줘", "할 일 정리해줘", "다음에 뭐 해야 해" 등을 요청할 때 활성화됩니다.
GitHub
sdd-workflow
SDD(Spec Driven Development) 자동화 워크플로우를 실행합니다. 사용자가 "다음 작업 진행해줘", "구현 시작해줘", "SDD 워크플로우 실행" 등을 요청할 때 활성화됩니다. 작업 분할, 계획서 작성, 구현, CI 검증까지 자동으로...
GitHub
spec-writing
요구사항을 분석하여 명세서와 사용자 스토리를 작성합니다. "명세 작성해줘", "요구사항 정리해줘", "스펙 문서 만들어줘", "사용자 스토리 작성해줘" 등을 요청할 때 활성화됩니다.
GitHub
implementation
작업 계획서를 기반으로 TDD 방식으로 구현을 진행합니다. "구현 시작해줘", "개발 진행해줘", "코드 작성해줘", "작업 시작" 등을 요청할 때 활성화됩니다.
GitHub
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user me...
GitHub
post-bug-reflection
Self-improvement workflow after fixing any bug. Analyzes root causes and updates project guidance (CLAUDE.md, skills, commands) to prevent similar bugs. MUST be invoked after completing any bug fix before marki...
GitHub
run-resource-design
Guide for designing Run resources in OptAIC. Use when creating PipelineRun, ExperimentRun, BacktestRun, PortfolioOptimizationRun, TrainingRun, InferenceRun, or MonitoringRun. Covers execution tracking, metrics,...
GitHub
specification-driven-development
This skill should be used when the user asks about "spec methodology", "specification workflow", "spec-driven development", "how to write specs", "spec best practices", "specification templates", or needs guida...
GitHub
backlog-moderator
Business moderator for backlog prioritization debates. Synthesizes Champion and Critic views into final rankings. Optimizes for team productivity and sustainable velocity.
GitHub
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
GitHub
complexity-gate
Estimate issue complexity before implementation to prevent timeouts. Uses cheap estimation to save expensive implementation tokens.
GitHub
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
GitHub
fix-planner
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
GitHub
feature-recovery
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
GitHub
feature-spec-moderator
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
GitHub
backlog-critic
Engineering critic for backlog prioritization debates. Challenges proposed rankings with feasibility concerns, hidden complexity, and realistic effort estimates.
GitHub
code-quality-analyst
Analyzes code changes for quality issues, code smells, SOLID violations, LLM-generated code problems, and refactoring opportunities. Reports findings with severity, evidence, and suggested fixes.
GitHub
fix-planner
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.