DevOps

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 extractionUse when: delegation-core selected Gemini, need Gemini's 1M+ token context window,batch processing or large document summarization requiredDO 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 andreproducible evidence.Triggers: bug hunting, defect detection, debugging, fix verification, bug fix,regression check, error investigation, defect documentationUse when: deep bug hunting needed, documenting defects, verifying fixes,systematic debugging requiredDO 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 boundsUse when: reviewing Rust code, auditing unsafe blocks, analyzing ownership patterns,scanning Cargo dependencies for securityDO 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 codeUse when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanupDO 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 graphUse when: auditing Makefiles, reviewing build system, checking portability,eliminating recipe duplicationDO 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 documentationUse when: README requires structural refresh, adding features to documentation,aligning readme with exemplar standards, improving project presentationDO 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 assessmentUse when: reviewing architecture decisions, auditing ADR compliance, analyzingcoupling, validating design principlesDO 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 summariesfrom any changeset.Triggers: diff analysis, changeset review, risk assessment, change categorization,semantic analysis, release preparation, change summary, git diffUse when: analyzing specific changesets, assessing risk of changes, preparingrelease notes, categorizing changes by type and impactDO 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 pressureUse 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 vulnerabilityUse when: auditing existing hooks for security vulnerabilities, benchmarkinghook performance, implementing hooks using Python SDK, understanding hookcallback signatures, validating hooks against compliance standardsDO 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 docsUse when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRsDO 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.

Complete guide for writing Claude Code and SDK hooks with security-first design.Triggers: hook creation, hook writing, PreToolUse, PostToolUse, UserPromptSubmit,tool validation, logging hooks, context injection, workflow automationUse when: creating new hooks for tool validation, logging operations for audit,injecting context before prompts, enforcing project-specific workflows,preventing dangerous operations in productionDO NOT use when: logic belongs in core skill - use Skills instead.DO NOT use when: complex multi-step workflows needed - use Agents instead.DO NOT use when: behavior better suited for custom tool.Use this skill BEFORE writing any hook. Check even if unsure.

Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.

Shared infrastructure and patterns for imbue analysis skills.Triggers: imbue patterns, todowrite patterns, evidence formats, analysis workflows,shared templates, imbue infrastructureUse when: other imbue skills need common patterns, creating new analysis skills,ensuring consistency across imbue pluginDO NOT use directly: this skill is infrastructure for other imbue skills.This skill provides shared patterns consumed by other imbue skills.

Generic weighted scoring and threshold-based decision framework for evaluatingartifacts against configurable criteria.Triggers: evaluation, scoring, quality gates, decision framework, rubrics,weighted criteria, threshold decisions, artifact evaluationUse when: implementing evaluation systems, creating quality gates, designingscoring rubrics, building decision frameworksDO NOT use when: simple pass/fail without scoring needs.Consult this skill when building evaluation or scoring systems.

Orchestrate and run appropriate pensive review skills based on codebaseanalysis and context.Triggers: code review, unified review, full review, review orchestration,multi-domain review, intelligent review, auto-detect reviewUse when: general review needed without knowing which specific skill applies,full multi-domain review desired, integrated reporting neededDO 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.

Foundational infrastructure patterns shared across all leyline skills.Triggers: leyline patterns, shared infrastructure, python imports, config patterns,leyline foundation, cross-skill patternsUse when: other leyline skills need common patterns, creating new infrastructureskills, ensuring consistency across leyline pluginDO NOT use directly: this skill is infrastructure for other leyline skills.This skill provides shared patterns consumed by other leyline skills.

Architecture-aware project initialization combining online research with archetype selection.Triggers: project initialization, new project, architecture decision, project setup,which architecture, choose architecture, project architectureUse when: initializing a new project and need to select an appropriate architecturebased on project type, team size, domain complexity, and current best practicesDO 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 storiesUse when: creating new specifications or writing acceptance criteriaDO NOT use when: generating implementation tasks - use task-planning.

Design and construct virtual memory palaces for spatial knowledge organizationusing mnemonic techniques.Triggers: memory palace, spatial organization, mnemonic, knowledge architecture,domain mapping, layout design, memory structure, recall enhancementUse when: creating new memory palace structures, organizing complex domains,designing spatial layouts for knowledge retentionDO 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.