持續整合/部署

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY principle, or mentions code smells like copy-paste, magic numbers, or repeated logic. Implements a 4-step workflow from identifying repetition to verified refactoring.

Aggregates and summarizes the latest AI news from multiple sources including AI news websites and web search. Provides concise news briefs with direct links to original articles. Activates when user asks for 'today's AI news', 'AI updates', 'latest AI developments', or mentions wanting a 'daily AI briefing'.

Systematic approach for creating minimal-change, reversible implementation plans. Claude invokes this skill when transforming requirements/research into executable blueprints. Emphasizes simplicity, safety, and clear verification steps.

Validates KCL Crossplane compositions with comprehensive checks including formatting, syntax validation, and rendering tests. Automatically activates when working with KCL files, Crossplane compositions, or before commits touching infrastructure/base/crossplane/configuration/. Prevents CI failures and catches critical bugs like the mutation pattern.

Orchestrate and run appropriate pensive review skills based on codebase analysis and context. Triggers: code review, unified review, full review, review orchestration, multi-domain review, intelligent review, auto-detect review Use when: general review needed without knowing which specific skill applies, full multi-domain review desired, integrated reporting needed DO NOT use when: specific review type known - use bug-review, test-review, etc. DO NOT use when: architecture-only focus - use architecture-review. Use this skill when orchestrating multiple review types.

Architecture-aware project initialization combining online research with archetype selection. Triggers: project initialization, new project, architecture decision, project setup, which architecture, choose architecture, project architecture Use when: initializing a new project and need to select an appropriate architecture based on project type, team size, domain complexity, and current best practices DO NOT use when: architecture is already decided - use project-init instead. DO NOT use when: exploring multiple architectures - use architecture-paradigms instead.

Create clear, testable specifications with user stories and acceptance criteria. Triggers: spec writing, feature specification, requirements, user stories Use when: creating new specifications or writing acceptance criteria DO NOT use when: generating implementation tasks - use task-planning.

Design and construct virtual memory palaces for spatial knowledge organization using mnemonic techniques. Triggers: memory palace, spatial organization, mnemonic, knowledge architecture, domain mapping, layout design, memory structure, recall enhancement Use when: creating new memory palace structures, organizing complex domains, designing spatial layouts for knowledge retention DO NOT use when: quick knowledge search - use knowledge-locator instead. DO NOT use when: session-specific context - use session-palace-builder. Consult this skill when designing permanent memory palace structures.

Reusable patterns and templates for Claude Code skill and hook development. Triggers: validation patterns, error handling, testing templates, workflow patterns, shared patterns, reusable templates, DRY patterns, common workflows Use when: creating new skills or hooks that need consistent patterns, implementing validation logic, setting up error handling, creating test scaffolding, referencing standard workflow structures DO NOT use when: pattern is specific to one skill only. DO NOT use when: pattern is still evolving - wait for stability. DO NOT use when: pattern is context-dependent requiring variations. Reference these patterns to validate consistency across the ecosystem.

Shared infrastructure and patterns for spec-kit specification-driven development. Triggers: spec-kit patterns, tech-stack patterns, checklist dimensions, artifact structure, specification infrastructure, shared templates Use when: developing new spec-kit skills, referencing standard patterns, ensuring consistency across specification workflows DO NOT use directly: this skill is infrastructure for other spec-kit skills. Provides reusable patterns consumed by all spec-kit commands and skills.

Compose processing stages using a pipes-and-filters model for ETL, media processing, or compiler-like workloads. Triggers: pipeline architecture, pipes and filters, ETL, data transformation, stream processing, CI/CD pipeline, media processing, batch processing Use when: data flows through fixed sequence of transformations, stages can be independently developed and tested, parallel processing of stages is beneficial DO NOT use when: selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: data flow isn't sequential or predictable. DO NOT use when: complex branching/merging logic dominates. Consult this skill when designing data pipelines or transformation workflows.

Serverless FaaS for event-driven workloads with minimal infrastructure management. Triggers: serverless, FaaS, Lambda, event-driven, pay-per-use Use when: workloads are event-driven with bursty traffic DO NOT use when: long-running processes or stateful operations required.

Guide to deciding whether to escalate from a lower model (haiku/sonnet) to a higher model (sonnet/opus). Triggers: model escalation, haiku to sonnet, sonnet to opus, reasoning depth, task complexity, model selection, capability trade-off Use when: evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment DO NOT use when: thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead. NEVER escalate without investigation first. This is the Iron Law.

Python testing with pytest, fixtures, mocking, and TDD workflows. Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage, test-driven development, testing patterns, parameterized tests Use when: writing unit tests, setting up test suites, implementing TDD, configuring pytest, creating fixtures, async testing DO NOT use when: evaluating test quality - use pensive:test-review instead. DO NOT use when: infrastructure test config - use leyline:pytest-config. Consult this skill for Python testing implementation and patterns.

Coarse-grained service architecture for deployment independence without microservices complexity. Triggers: service-based, SOA, coarse-grained services, domain services Use when: teams need deployment independence without microservices complexity DO NOT use when: fine-grained scaling needed - use microservices.

Qwen CLI delegation workflow implementing delegation-core for Alibaba's Qwen models. Triggers: qwen cli, qwen delegation, alibaba qwen, qwen batch, multi-file analysis, qwen summarization, qwen extraction, 100K context Use when: delegation-core selected Qwen, need Qwen's large context capabilities, batch processing or multi-file analysis required DO NOT use when: deciding which model to use - use delegation-core first. DO NOT use when: qwen CLI not installed or configured. Consult this skill when implementing Qwen-specific delegation workflows.

detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

Single deployable with enforced module boundaries for team autonomy without distributed complexity. Triggers: modular monolith, module boundaries, single deployment, team autonomy Use when: teams need autonomy without distributed overhead DO NOT use when: already using microservices or system is small.

CQRS and Event Sourcing for auditability, read/write separation, and temporal queries. Triggers: CQRS, event sourcing, audit trail, temporal queries Use when: read/write scaling differs or audit trail required DO NOT use when: simple CRUD - use architecture-paradigms first.