Git & Version Control

GitOps workflow automation for trunk-based development, branch strategy, release management, and deployment patterns. Use when setting up repositories, planning release strategies, or configuring CI/CD pipelines.

This skill should be used when the user asks to "verify reproducibility", "confirm the results", "prove it's reproducible", or as Phase 5 of the /ds workflow before claiming completion. Checks reproducibility and requires user acceptance.

Best practices for creating Shopify 2.0 sections with inline CSS and JavaScript

This skill should be used when working with browser-rendered artifacts (i.e. Bun, React/React Native) to proactively validate that development work on localhost is being built appropriately and to support debugging browser-rendered content. Use this skill after making frontend changes to verify the output visually.

Coordinates agent assignments, validates merge states, and manages ticket lifecycle.

Write TypeScript for Web Components and Node.js with strict typing. Use when adding types to JavaScript projects, building type-safe APIs, or creating generic utilities.

Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.

Master the Purify library for practical functional programming in TypeScript with algebraic data types (Maybe, Either, EitherAsync, MaybeAsync), composable error handling, data transformations, Codec for runtime type safety, List operations, Tuple utilities, and functional patterns. Use when working with Purify's Maybe/Either types, async error handling with EitherAsync/MaybeAsync, runtime validation with Codecs, or building practical functional TypeScript applications with cleaner syntax than fp-ts.

Write strategic, focused tests for critical user flows and core functionality using modern testing frameworks, focusing on behavior over implementation. Use this skill when creating test files, writing unit tests, integration tests, or end-to-end tests in test directories (tests/, __tests__, spec/, *.test.js, *.spec.py). Apply this skill when testing core user workflows and business-critical features, implementing test-driven development (TDD) with red-green-refactor cycles, mocking external dependencies for isolated unit tests, using clear descriptive test names that explain expected behavior, following arrange-act-assert patterns, and ensuring tests run fast and independently. This skill prioritizes testing what matters most (primary user flows) while deferring edge cases and non-critical paths until later, emphasizes behavior testing over implementation details to reduce brittleness, and uses modern frameworks like Jest, Playwright, Cypress, pytest, RSpec, or Testing Library for reliable, maintainable test

Extract Power BI PBIR visuals into reusable templates. Use when users want to save an existing visual configuration as a template, standardize visual formats across projects, or add new visual types to the template library.

Follow development best practices for project organization, version control, documentation, environment configuration, and dependency management to maintain consistency across the team. Use this skill when organizing project files and directory structures, writing or updating README files and documentation, working with git commits and branches, configuring environment variables, managing dependencies in package.json or requirements.txt, or establishing code review processes. Use this skill when working with configuration files, .env files, documentation files, or when setting up CI/CD workflows. Use this skill when implementing feature flags, maintaining changelogs, or establishing team development workflows and contribution guidelines.

プロジェクトのブランチ命名規則に従ってGitブランチを作成。「ブランチお願い」「ブランチを作って」「ブランチ作って」「ブランチを切って」「新しいブランチで作業」などと言われた時、または新しい作業・機能開発・バグ修正を開始する前に使用

Testing and quality validation for Flutter code.USE WHEN: creating tests, verifying coverage, running E2E tests,validating code quality, checking test coverage thresholds.Minimum coverage: 80% overall, 95% services, 70% widgets.Examples:<example>Context: The user implemented a new feature.user: "I've just implemented the new itinerary creation service"assistant: "I'll use testing-agent to generate comprehensive tests and ensure quality."<commentary>New code needs testing - use testing-agent.</commentary></example><example>Context: The user wants to run E2E tests.user: "Run the E2E tests to validate the login flow"assistant: "I'll use testing-agent to execute E2E tests with MCP Chrome DevTools."<commentary>E2E testing is a testing-agent responsibility.</commentary></example>

CellCharter spatial transcriptomics analysis toolkit - complete documentation with precise file name-based categorization

Système de gestion de tâches avec workflows Git, analyse comparative, et priorisation intelligente. Activer ce skill quand l'utilisateur parle de tâches, backlog, analyses de CV, ou demande quelle tâche faire ensuite.

Standardizing and formatting datasets for Unsloth, including chat template conversion and synthetic data generation (triggers: chat templates, ShareGPT, Alpaca, conversation_extension, add_new_tokens, standardize_sharegpt, formatting_prompts_func).

Implement or extend a user-facing workflow in a web application, integrating with existing backend APIs. Use when the feature is primarily a UI/UX change backed by existing APIs, affects only the web frontend, and requires following design system, routing, and testing conventions.

Commitlint configuration and GitHub Copilot commit message instruction templates with validation logic for conventional commit enforcement. Includes 6 required standards (conventional format, relaxed subject rules for Copilot compatibility, optional scope, Husky integration, required dependencies, Copilot instruction consistency). Use when creating or auditing commitlint.config.js and .copilot-commit-message-instructions.md files.

Generate PR documentation with UML diagrams based on Git branch differences. Explains modification reasons, content, and implementation. Uses Mermaid to draw architecture, class, sequence diagrams with exact code element names matching actual code.

Use when modifying MCP servers that touch repo memory (especially docs-memory). Includes protocol guardrails, validation ladder, and how to store new capabilities as Skills so future agents don’t re-learn painful details. Triggers: docs-memory, mcp-server.js, tools/list, tools/call, stdio, headerless, JSON-RPC, protocol.