Content & Media

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.

Evaluate and upgrade test suites with TDD/BDD rigor, coverage tracking, and quality assessment. Triggers: test audit, test coverage, test quality, TDD, BDD, test gaps, test improvement, coverage analysis, test remediation Use when: auditing test suites, analyzing coverage gaps, improving test quality, evaluating TDD/BDD compliance DO NOT use when: writing new tests - use parseltongue:python-testing. DO NOT use when: updating existing tests - use sanctum:test-updates. Use this skill for test suite evaluation and quality assessment.

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.

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.

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.

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 automation Use when: creating new hooks for tool validation, logging operations for audit, injecting context before prompts, enforcing project-specific workflows, preventing dangerous operations in production DO 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.

Construct temporary, session-specific memory palaces for complex projects and conversations. Triggers: session context, project memory, conversation state, temporary storage, session palace, context preservation, complex project, extended conversation Use when: working on complex multi-step projects, preserving context across interruptions, tracking session-specific state DO NOT use when: permanent knowledge structures needed - use memory-palace-architect. DO NOT use when: searching existing knowledge - use knowledge-locator. Consult this skill for session-scoped temporary knowledge structures.

Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling. Triggers: delegate task, external LLM, gemini, qwen, large context, offload Use when: tasks exceed context window or need cheaper processing DO NOT use when: task requires Claude's reasoning.

Monitor and optimize CPU/GPU usage with load measurement and cost-effective validation strategies. Triggers: CPU usage, GPU usage, performance, load monitoring, build performance, training, resource consumption, test suite, compilation Use when: session starts (auto-load with token-conservation), planning builds or training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commands DO NOT use when: simple operations with no resource impact. DO NOT use when: quick single-file operations. Use this skill BEFORE resource-intensive operations. Establish baselines proactively.

Foundational workflow for preparing and structuring detailed reviews (architecture, API, code quality). Triggers: review workflow, structured review, review scaffolding, evidence capture, review preparation, analysis framework, review template Use when: starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs DO NOT use when: quick catchup without formal review - use catchup. DO NOT use when: diff-focused analysis - use diff-analysis. Use this skill at the BEGINNING of any detailed review for consistent structure.

Model system responsibilities across clients, servers, and optional peer-to-peer nodes for traditional distributed applications. Triggers: client-server, web architecture, mobile backend, API design, thin client, thick client, peer-to-peer, P2P, offline-first, synchronization Use when: traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed DO NOT use when: selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns. Consult this skill when designing client-server systems or API architectures.

Structured file enumeration and content analysis for understanding codebase structure before reviews or refactoring. Triggers: file analysis, codebase structure, directory mapping, hotspot detection, code exploration, file enumeration, structure mapping, module boundaries Use when: before architecture reviews to understand file organization, exploring unfamiliar codebases to map structure, estimating scope for refactoring or migration DO 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 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.

System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.

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.

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.

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.