Skill UI

Automates generation and execution of API endpoint tests for REST and GraphQL services, covering CRUD operations, authentication workflows, OpenAPI contract validation, and response verification (status, headers, body).

Automates generation and execution of API endpoint tests for REST and GraphQL services, covering CRUD operations, authentication workflows, OpenAPI contract validation, and response verification (status, headers, body).

This skill generates commit messages strictly following Sentry's conventions and the Conventional Commit format. It mandates a structured commit message including a type, scope, subject, body (explaining what and why), and a footer for issue references. Use this whenever committing code changes to ensure a highly readable, traceable, and standardized version history.

This guide outlines the process of migrating codebase dependencies and logic when upgrading the Ideogram API from legacy versions (V1/V2) to the robust V3 endpoints. It addresses critical breaking changes, including the shift from JSON body to multipart/form-data, changes in model naming, aspect ratio syntax, and the integration of new V3 features like rendering speed and style presets. Provides structured code adapters for smooth transition.

This guide details the recommended pattern for managing per-project plugin settings and state within a development environment. Plugins store their configuration in a dedicated `.claude/plugin-name.local.md` file. This file utilizes YAML frontmatter for structured settings (like enabling flags, retry counts, and parameters) and a Markdown body for additional context or instructions. It provides techniques for reading these settings using Bash hooks, commands, and agents.

Guides API developers through building request body validators, following best practices for REST, GraphQL, and OpenAPI workflows, and generating production-ready code plus validations.

Write terse, intent-only Conventional Commits messages. Use for generating commit messages from diffs or summaries, with optional scope, imperative mood, and concise body only when needed.

This workflow guides developers through generating standardized, descriptive commit messages using the Conventional Commits specification. It provides a structured XML template (including type, scope, description, body, and footer) and integrates directly into the Git workflow, ensuring project history is clean, traceable, and machine-readable. Ideal for maintaining large, collaborative codebases.

This tool automates the entire workflow of creating a GitHub Pull Request (PR) directly from a structured specification file. It analyzes the template, extracts requirements, checks for existing PRs, creates the draft, updates the body and title with specification details, and finally transitions the PR state to 'Ready for Review'. This significantly streamlines the feature request submission process, ensuring all necessary documentation and metadata are included.

This guide provides a comprehensive framework for adopting Conventional Commits using Mandarin Chinese. It details rules for commit types (feat, fix, perf, etc.), structuring the subject, body, and footer messages. Furthermore, it covers integrating automated tools like husky, commitlint, and conventional-changelog to enforce standardized, professional, and traceable commit workflows for Chinese development teams.

A comprehensive guide and implementation pattern for querying, searching, and paginating OneNote content using the Microsoft Graph API. This skill addresses the limitations of the standard OneNote search endpoint, providing robust methods for cross-notebook querying, advanced OData filtering on metadata, and client-side full-text indexing for body content. Ideal for building complex knowledge retrieval systems that handle large, distributed result sets.

This skill creates a comprehensive, three-column documentation page in pure HTML. It is ideal when the brief requires a professional "guide," "tutorial," or "API reference." It includes structured elements like a sticky left navigation sidebar, a main article body, and a dynamic right Table of Contents, ensuring technical content is highly readable and navigable.