Git & Version Control

Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).

Generate comprehensive pytest test suites for CasareRPA components, including nodes, controllers, use cases, and domain entities. Use when: creating new tests, testing nodes, controller tests, use case tests, domain entity tests, test coverage needed, pytest test generation.

This skill should be used when the user asks to "design MCP tool", "create tool schema", "tool best practices", "input validation", "output schema", "error handling for tools", or discusses designing individual MCP tools with proper schemas and responses.

Advise on technology choices for new full-stack projects using the user's preferred stack (FastAPI + React + PostgreSQL). Use when starting a new project, discussing architecture decisions, choosing frameworks, scaffolding an application, or when the user asks what stack to use.

Pre-deployment verification for young-personal-site.Ensures build success, TypeScript, i18n sync, and functionality.

Generate optimized Dockerfiles with multi-stage builds and best practices. Use when containerizing applications or creating Docker configurations.

Bundle and share code as gists or markdown. Use to create shareable code bundles, extract imports, and create GitHub gists.

Create GitHub pull request with atomic Beads issue closure. MUST BE USED for opening PRs.Asks if work is complete - if YES, closes Beads issue BEFORE creating PR (JSONL merges atomically with code).If NO, creates draft PR with issue still open. Automatically links Beads tracking and includes Feature-Key.Use when user wants to open a PR, submit work for review, merge into master, or prepare for deployment,or when user mentions "ready for review", "create PR", "open PR", "merge conflicts", "CI checks needed","branch ahead of master", PR creation, opening pull requests, deployment preparation, or submitting for team review.

This skill should be used when starting any feature or bug fix, exploring unfamiliar code, making commits or PRs, or when unsure which agent or approach to use. Covers agent routing, git discipline, testing workflow, and proactive quality practices.

This skill should be used when educators, trainers, curriculum designers, or instructional designers need to create comprehensive lesson plans from a topic. The skill generates structured educational content with learning objectives aligned to Bloom's taxonomy, content outlines, interactive exercises, assessment quizzes, and instructor notes. It can read existing .docx and .pptx files for context and exports final lesson plans as .docx files. Triggers include requests to create lesson plans, generate curriculum, build training materials, or develop educational content.

Clean up local git branches marked as [gone] (deleted on remote but still exist locally). Use when the user wants to clean up stale branches, remove gone branches, or delete branches that no longer exist on remote.

Applies the DigitalVisionWorks professional theme to components, pages, and artifacts. Use when creating new UI elements, ensuring visual consistency, or styling components. Triggers on theming requests, style consistency checks, or new component creation.

Generates GDScript Custom Resource files from structured JSON schemas using R&D framework. Converts parse-tbl output to idiomatic Godot resources with proper type mapping and validation.

当用户要求提交代码、保存到 GitHub、推送改动、创建 PR 或同步代码时使用

Follow consistent code formatting, naming conventions, TypeScript standards, and Astro component structure patterns across the entire codebase. Use this skill when writing any code file to ensure proper formatting, naming, indentation, and style consistency. When working on TypeScript files (.ts, .tsx), Astro components (.astro), React/Vue/Svelte components, configuration files, utility functions, type definitions, import statements, prop interfaces, or any code that requires formatting with Prettier or linting with ESLint.

This skill should be used when the user wants to commit their work to git and push to GitHub. It guides through reviewing changes, crafting meaningful commit messages following project conventions (including Conventional Commits when detected), creating commits with security checks, and pushing to remote repositories.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

Maintain code quality using Biome linting, formatting, and git hooks. Use this when the user asks about linting errors, code formatting, Biome configuration, fixing code style issues, organizing imports, or ensuring code quality standards before commits.

Multi-tool orchestration patterns for complex Bluera Knowledge operations. Teaches progressive library exploration, adding libraries with job monitoring, handling large result sets, multi-store searches, and error recovery workflows.

Automatically runs project validation commands (linters, type checkers, tests) after file edits and blocks commits on any failure. Reads validation commands from CLAUDE.md or auto-detects from project type. Enforces strict quality gates to catch issues early. (project)