持續整合/部署

Declarative release readiness checklist that mirrors GitHub checks, deployment issues, and documentation requirements. Triggers: release gates, release readiness, deployment checklist, release review, quality signals, rollout scorecard, QA handshake, deployment gates Use when: preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs DO NOT use when: weekly status updates - use github-initiative-pulse. DO NOT use when: code reviews - use pensive review skills. Standardizes release approvals with GitHub-aware checklists.

Retrospective workflow evaluation and improvement of skills, agents, commands, and hooks. Triggers: workflow improvement, retrospective, workflow efficiency Use when: workflow felt slow, confusing, or needs optimization DO NOT use when: implementing features - focus on feature work first.

Employ the Hexagonal (Ports & Adapters) pattern to decouple domain logic from infrastructure, maximizing flexibility and testability. Triggers: hexagonal architecture, ports and adapters, infrastructure independence, dependency inversion, clean architecture, domain isolation, adapter pattern, infrastructure abstraction, database independence, framework independence Use when: designing systems with strong business logic separation, anticipating infrastructure changes, needing easy mocking for tests, building portable domain code DO NOT use when: selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: building simple CRUD apps without complex domain logic. Consult this skill when implementing hexagonal patterns or migrating to port-based design.

Design skills as modular building blocks for predictable token usage. Triggers: skill design, skill architecture, modularization, token optimization, skill structure, refactoring skills, new skill creation, skill complexity Use when: creating new skills that will be >150 lines, breaking down complex monolithic skills, planning skill architecture, refactoring overlapping skills, reviewing skill maintainability, designing skill module structure DO NOT use when: evaluating existing skill quality - use skills-eval instead. DO NOT use when: writing prose for humans - use writing-clearly-and-concisely. DO NOT use when: need improvement recommendations - use skills-eval. Use this skill BEFORE creating any new skill. Check even if unsure.

Shared infrastructure and reusable modules for all pensive review skills. Triggers: pensive patterns, review workflow, output templates, quality checklists, pensive infrastructure, shared review patterns Use when: other pensive skills need common patterns, creating new review skills, ensuring consistency across pensive plugin DO NOT use directly: this skill is infrastructure for other pensive skills. This skill provides shared patterns consumed by other pensive skills.

CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.

Transform project brief into detailed, testable specifications using spec-driven development methodology

Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. Triggers: task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specifications - use spec-writing.

Gemini CLI delegation workflow implementing delegation-core for Google's Gemini models. Triggers: gemini cli, gemini delegation, google gemini, 1M context, large file analysis, gemini batch, gemini summarization, gemini extraction Use when: delegation-core selected Gemini, need Gemini's 1M+ token context window, batch processing or large document summarization required DO NOT use when: deciding which model to use - use delegation-core first. DO NOT use when: gemini CLI not installed or authenticated. Consult this skill when implementing Gemini-specific delegation workflows.

Systematically uncover and fix bugs using language-specific expertise and reproducible evidence. Triggers: bug hunting, defect detection, debugging, fix verification, bug fix, regression check, error investigation, defect documentation Use when: deep bug hunting needed, documenting defects, verifying fixes, systematic debugging required DO NOT use when: test coverage audit - use test-review instead. DO NOT use when: architecture issues - use architecture-review. Use this skill for systematic bug hunting with evidence trails.

Expert-level Rust audits covering ownership, concurrency, unsafe blocks, traits, and Cargo dependencies. Triggers: Rust review, ownership analysis, borrowing, unsafe audit, concurrency, Cargo dependencies, lifetime annotations, trait bounds Use when: reviewing Rust code, auditing unsafe blocks, analyzing ownership patterns, scanning Cargo dependencies for security DO NOT use when: general code review without Rust - use unified-review. DO NOT use when: performance profiling - use parseltongue:python-performance pattern. Use this skill for Rust-specific code audits.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, and documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, redundancy, codebase health, technical debt, unused code Use when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanup DO NOT use when: actively developing new features, time-sensitive bug fixes. DO NOT use when: codebase is < 1000 lines (insufficient scale for bloat). Progressive 3-tier detection: quick scan → targeted analysis → deep audit.

Audit Makefiles for duplication, portability, and idiomatic GNU Make usage. Triggers: Makefile review, build system, GNU Make, portability, deduplication, pattern rules, automatic variables, dependency graph Use when: auditing Makefiles, reviewing build system, checking portability, eliminating recipe duplication DO NOT use when: creating new Makefiles - use abstract:make-dogfood. DO NOT use when: architecture review - use architecture-review. Use this skill for Makefile audit and optimization.

Consolidate README content using language-aware exemplars, internal doc linkage, and reproducible evidence. Triggers: README update, documentation refresh, readme structure, exemplar research, language-aware docs, readme modernization, project documentation Use when: README requires structural refresh, adding features to documentation, aligning readme with exemplar standards, improving project presentation DO NOT use when: updating inline docs - use doc-updates. DO NOT use when: consolidating ephemeral reports - use doc-consolidation. Run git-workspace-review first to capture repo context.

Evaluate codebase architecture against ADRs, coupling rules, and team guardrails. Triggers: architecture review, ADR audit, coupling analysis, design review, principle checks, Law of Demeter, architecture assessment Use when: reviewing architecture decisions, auditing ADR compliance, analyzing coupling, validating design principles DO NOT use when: selecting architecture paradigms - use archetypes skills. DO NOT use when: API surface review - use api-review. Use this skill for architecture assessment and compliance.

Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.

MECW theory and patterns for hallucination prevention via context management. Implements 50% rule. Triggers: MECW, context window, hallucination, 50% rule, context pressure Use when: implementing context-aware systems or monitoring context pressure

detailed hook evaluation framework for Claude Code and Agent SDK hooks. Triggers: hook audit, hook security, hook performance, hook compliance, SDK hooks, hook evaluation, hook benchmarking, hook vulnerability Use when: auditing existing hooks for security vulnerabilities, benchmarking hook performance, implementing hooks using Python SDK, understanding hook callback signatures, validating hooks against compliance standards DO NOT use when: deciding hook placement - use hook-scope-guide instead. DO NOT use when: writing hook rules from scratch - use hookify instead. DO NOT use when: validating plugin structure - use validate-plugin instead. Use this skill BEFORE deploying hooks to production.

Update documentation with writing guideline enforcement, consolidation detection, and accuracy verification. Triggers: documentation update, docs update, ADR, docstrings, writing guidelines, readme update, debloat docs Use when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRs DO NOT use when: README-specific updates - use update-readme instead. DO NOT use when: complex multi-file consolidation - use doc-consolidation. Use this skill for general documentation updates with built-in quality gates.

Generate language-specific Makefile with common development targets