CI/CD

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.

Configure GitHub Actions workflows for CI/CD (test, lint, typecheck, publish)

Structured file enumeration and content analysis for understanding codebasestructure before reviews or refactoring.Triggers: file analysis, codebase structure, directory mapping, hotspot detection,code exploration, file enumeration, structure mapping, module boundariesUse when: before architecture reviews to understand file organization, exploringunfamiliar codebases to map structure, estimating scope for refactoring or migrationDO NOT use when: general code exploration - use the Explore agent.DO NOT use when: searching for specific patterns - use Grep directly.Provides structural context for downstream review and refactoring workflows.

Update and maintain tests following TDD/BDD principles with detailedquality assurance.Triggers: test updates, test maintenance, test generation, TDD workflow,BDD patterns, test coverage, pytest, test enhancement, quality assuranceUse when: updating existing tests, generating new tests for features,enhancing test quality, ensuring detailed coverage, pre-commit validationDO 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.

Intensive mathematical analysis for numerical stability, algorithm correctness,and alignment with authoritative standards.Triggers: math review, numerical stability, algorithm correctness, mathematicalverification, scientific computing, numerical analysis, derivation checkUse when: reviewing math-heavy code, verifying algorithm correctness, checkingnumerical stability, aligning with mathematical standardsDO NOT use when: general algorithm review - use architecture-review.DO NOT use when: performance optimization - use parseltongue:python-performance.Use this skill for mathematical code verification.

Use a Layered (N-Tier) architecture to separate presentation, domain logic, anddata access responsibilities within a system.Triggers: layered architecture, n-tier, separation of concerns, presentation layer,data access layer, service layer, traditional architecture, monolith structure,layer enforcement, dependency directionUse when: building traditional applications with clear boundaries, working withmoderate-sized teams, needing familiar and well-understood patterns, compliancerequirements demand clear separationDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: high scalability needs independent component scaling.DO NOT use when: teams need independent deployment cycles - use microservices.Consult this skill when implementing layered patterns or enforcing layer boundaries.

Decompose systems into a suite of small, independently deployable services alignedto specific business capabilities.Triggers: microservices, service decomposition, independent deployment, team autonomy,distributed system, API gateway, service mesh, bounded contexts, polyglot persistenceUse when: teams need high autonomy and independent releases, different capabilitieshave distinct scaling needs, strong DevOps/SRE maturity exists, polyglot tech stacks neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: small team with low organizational complexity.DO NOT use when: lack of DevOps maturity or limited platform engineering resources.DO NOT use when: strong transactional consistency required across operations.Consult this skill when designing or evolving microservices architectures.

Evaluate and improve Claude skill quality through auditing.Triggers: skill audit, quality review, compliance check, improvement suggestions,token usage analysis, skill evaluation, skill assessment, skill optimization,skill standards, skill metrics, skill performanceUse when: reviewing skill quality, preparing skills for production, auditingexisting skills, generating improvement recommendations, checking compliancewith standards, analyzing token efficiency, benchmarking skill performanceDO NOT use when: creating new skills from scratch - use modular-skills instead.DO NOT use when: writing prose for humans - use writing-clearly-and-concisely.DO NOT use when: need architectural design patterns - use modular-skills.Use this skill BEFORE shipping any skill to production. Check even if unsure.

Enforces "prove before claim" discipline - validation, testing, and evidencerequirements before declaring work complete.Triggers: completion, finished, done, working, should work, configured,ready to use, implemented, fixedUse when: claiming ANY work is complete, recommending solutions, statingsomething will work, finishing implementationsDO NOT use when: explicitly asking questions or requesting clarificationDO NOT use when: work is clearly in-progress and not claiming completionCRITICAL: This skill is MANDATORY before any completion claim. Violationsresult in wasted time and eroded trust.

Guide to effective Claude Code skill authoring using TDD methodology andpersuasion principles.Triggers: skill authoring, skill writing, new skill, TDD skills, skill creation,skill best practices, skill validation, skill deployment, skill complianceUse when: creating new skills from scratch, improving existing skills withlow compliance rates, learning skill authoring best practices, validatingskill quality before deployment, understanding what makes skills effectiveDO NOT use when: evaluating existing skills - use skills-eval instead.DO NOT use when: analyzing skill architecture - use modular-skills instead.DO NOT use when: writing general documentation for humans.YOU MUST write a failing test before writing any skill. This is the Iron Law.

Workflow for capturing evidence and citations to create reproducible analysesand audit trails.Triggers: evidence capture, citations, reproducible analysis, audit trail,documentation, evidence logging, findings documentationUse when: conducting any review that needs evidence trails, creating auditdocumentation, ensuring reproducibility of analysesDO NOT use when: quick informal checks without documentation needs.DO NOT use when: structured output is the focus - use structured-output.Use this skill as foundation for all evidence-based review workflows.

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 optimizationUse 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.