Git & Version Control

Update and maintain tests following TDD/BDD principles with detailed quality assurance. Triggers: test updates, test maintenance, test generation, TDD workflow, BDD patterns, test coverage, pytest, test enhancement, quality assurance Use when: updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation DO NOT use when: auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first. Run git-workspace-review first to understand which tests need updates.

Generic template patterns and lifecycle stages for knowledge storage, configuration management, and structured documentation. Triggers: storage templates, lifecycle stages, maturity progression, naming conventions, knowledge storage, configuration templates, documentation patterns Use when: organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions DO NOT use when: simple storage without lifecycle or structure needs. Consult this skill when designing storage and documentation systems.

Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. Triggers: speckit workflow, spec driven development, speckit commands Use when: starting any /speckit-* command or coordinating multi-phase development

Fix GitHub issues using subagent-driven-development with parallel execution where appropriate. Triggers: fix issue, github issue, issue resolution, subagent development, parallel execution, issue workflow, gh issue, fix github Use when: addressing GitHub issues systematically, multiple related issues need fixing, tasks can be parallelized across subagents, quality gates needed between task batches DO NOT use when: single simple fix - just implement directly. DO NOT use when: issue needs clarification - comment first to clarify scope. Uses subagents for parallel execution with code review gates between batches.

Methodology for summarizing changes, extracting insights, and identifying follow-up actions. Triggers: catchup, what changed, summarize changes, context acquisition, handoff, progress review, recent changes, git log analysis, sprint summary Use when: resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context DO NOT use when: doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead. Use this skill to quickly understand "what changed and what matters".

Development tooling standards including Deno runtime, JSR package registry, and configuration files. Use when setting up projects, managing dependencies, or configuring build tools.

Transform tool-heavy workflows into MCP code execution patterns for token savings and optimized processing. Triggers: MCP, code execution, tool chain, data pipeline, tool transformation, batch processing, workflow optimization Use when: >3 tools chained sequentially, large datasets (>10k rows), large files (>50KB), context usage >25% DO NOT use when: simple tool calls that don't chain. DO NOT use when: context pressure is low and tools are fast. Use this skill BEFORE building complex tool chains. Optimize proactively.

Lightweight preflight checklist for verifying repo path, staged changes, and diffs before other workflows. Triggers: git status, preflight, workspace check, staged changes, diff review, git verification, repo state Use when: verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs DO NOT use when: full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep. Use this skill as foundation for git workflows.

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.

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.

Scope-focused PR code review that validates against original requirements and routes out-of-scope findings to GitHub issues. Triggers: PR review, pull request review, scope validation, requirement compliance, backlog triage, code review, blocking issues Use when: reviewing PRs, validating against requirements, triaging findings to backlog, preventing overengineering DO NOT use when: preparing PRs - use pr-prep instead. DO NOT use when: deep code review - use pensive:unified-review. Use this skill for scope-focused PR reviews.

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.

Consolidates ephemeral LLM-generated markdown files into permanent documentation. Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup, report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md files Use when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews DO NOT use when: files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value. Merges valuable content into permanent documentation, then deletes source files.

Leveraging AI coding assistants and tools to boost development productivity, while maintaining oversight to ensure quality results.

Creates a new ButterCut release with version bump, changelog, git tag, gem build, and GitHub release. Use when publishing a new version.

A skill to automatically download and install the latest ButterCut version from GitHub while preserving libraries. Use when user wants to check for updates or update their installation for new features.

GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.

Generate images using Nano Banana Pro (Gemini 3 Pro Preview). Use when creating app icons, logos, UI graphics, marketing banners, social media images, illustrations, diagrams, or any visual assets. Supports reference images for style transfer and character consistency. Triggers include phrases like 'generate an image', 'create a graphic', 'make an icon', 'design a logo', 'create a banner', 'same style as', 'keep the style', or any request needing visual content.

GitHub PR workflow automation including fetching unresolved comments, resolving review threads, and parallel comment resolution. Use this skill when working with PR reviews, addressing reviewer feedback, or automating PR comment workflows.

Expert-level Home Assistant configuration management with efficient deployment workflows (git and rapid scp iteration), remote CLI access via SSH and hass-cli, automation verification protocols, log analysis, reload vs restart optimization, and comprehensive Lovelace dashboard management for tablet-optimized UIs. Includes template patterns, card types, debugging strategies, and real-world examples.