tooling-standards
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.
Discover databases git workflows skills, compare source repositories and read the instructions for each workflow.
Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.
Convert user stories to GitHub issues. Use when ready to create issues. Triggers on: create github issues, export to github, generate issues.
Use when managing Codex review iterations for a PR and you must enforce preflight risk-layer checks and post-merge learning capture.
This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktree...
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow t...
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers...
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to i...
Example Skillset that demonstrates inline + GitHub + registry dependencies.
Configure TDD enforcement via pre-commit hooks and CI coverage gates. Use when setting up test-first development workflow, adding coverage gates, or enforcing TDD practices.
Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.
Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.
Configure TDD enforcement via pre-commit hooks and CI coverage gates. Use when setting up test-first development workflow, adding coverage gates, or enforcing TDD practices.
Guidelines for pull requests descriptions. Use when asked to create a PR, or decided to create one by yourself, or when asked to write/improve PR description.
Update an existing pull request with new changes or respond to review feedback. Use when addressing PR comments, making requested changes, or updating a PR after review.
Review code changes for quality, correctness, and best practices. Use when asked to review a PR, review changes, or assess code quality before merge.
Create a pull request from the current branch. Use when changes are ready for review, when asked to submit work, or when explicitly asked to create a PR.
Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles....
GitLab 開發者評估與分析技能,使用 gl-cli.py 工具分析開發者的程式碼品質、提交歷史、專案參與度與技術水平,並產生綜合評估報告。
Turborepo monorepo management. Use when working with workspaces, build pipelines, caching, or monorepo-wide operations.
Code review guidelines and checklist. Use when reviewing PRs or preparing code for review.
Git branching and commit best practices. Use when working with git branches, commits, or merges.
Use when setting up CI/CD, implementing versioning, optimizing workflows, or managing releases with monorepo development workflows including version management, publishing, and team collaboration practices.
Use when writing commit messages that clearly communicate changes and tell the story of development. Helps create informative, well-structured commit messages that serve as documentation.
Use when configuring GitLab CI/CD variables, managing secrets, or integrating with external secret providers. Covers secure credential handling.
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.