github-workflow
GitHub-first workflow - Issues, PRs, milestones, auto-tracking for solo developer productivity
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
GitHub-first workflow - Issues, PRs, milestones, auto-tracking for solo developer productivity
Documentation standards and automation. Use when updating docs, writing guides, or synchronizing code with documentation.
This skill should be used when reviewing code or preparing code for review. It provides guidelines for what to look for in reviews, how to write constructive feedback, and standards for review comments.
Git best practices, commit conventions, branching strategies, and pull request workflows. Use when working with git operations, commits, branches, or PRs.
Validates all documentation references - file paths, links, line numbers, code examples
Security best practices, API key management, input validation. Use when handling secrets, user input, or security-sensitive code.
Python code quality standards (PEP 8, type hints, docstrings). Use when writing Python code.
This skill should be used when designing system architecture, making architectural decisions, or evaluating design patterns. It provides guidance on common patterns, ADR templates, design principles, and tradeo...
Create QDUOJ online judge problems (single or batch) with proper format. Use when user mentions creating QDUOJ problems, coding challenges, test cases, or OJ import.
This skill should be used when the user asks to "execute the plan", "run the plan", "implement the plan", or wants to follow through on a plan created by /write-plan.
This skill should be used when the user asks to "brainstorm", "design a feature", "think through an idea", "help me plan", or has a vague concept that needs refining into a technical specification through colla...
This skill should be used when the user asks to "write a plan", "create an implementation plan", "plan this feature", or has an approved design that needs to be broken into executable tasks for implementation.
This skill should be used when the user asks to "generate a changelog", "update changelog", "create release notes", or needs help documenting changes between versions using git history and tags.
Look up the latest version of any package using deps.dev API. Use this skill when checking package versions, updating dependencies, adding new packages to a project, or when the user asks about the current vers...
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creat...
Create, alter, and validate Snowflake semantic views using the Snowflake CLI (`snow`). Use when asked to build or troubleshoot semantic views or semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to va...
ADVISORY validation of code against design principles, accessibility, and best practices that linters cannot fully enforce. Use after linter passes and tests pass to validate design quality. Categorizes finding...
META ORCHESTRATOR for complete implementation workflow - design, test, lint, refactor, review, commit. Use for any code change that should result in a commit (features, bug fixes, refactors). Ensures clean code...
Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain....
Principles and patterns for writing effective React tests with Jest and React Testing Library. Use during implementation for test structure guidance, choosing test patterns, and deciding testing strategies. Emp...
Linter-driven refactoring patterns to reduce complexity and improve code quality in React/TypeScript. Use when ESLint fails with SonarJS complexity issues (cognitive, cyclomatic, expression) or when code feels...
Domain type design and architectural planning for Go code. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring reveals need for new types. Focuse...
ADVISORY validation of code against design principles that linters cannot enforce. Loaded by go-code-reviewer agent for design analysis guidance. Also invoked by @refactoring (after pattern application). Can be...
WHEN: User requests Go code work (implement, fix, add, refactor) or mentions @ldd in a Go project. Orchestrates complete workflow (Phases 1-5): design → test → implement → lint → fix → documentation. Auto-trigg...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.