Development

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.

Configure comprehensive three-layer pre-commit quality system with linting, type checking, and testing enforcement

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 remediationUse when: auditing test suites, analyzing coverage gaps, improving testquality, evaluating TDD/BDD complianceDO 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.

Scope-focused PR code review that validates against original requirements androutes out-of-scope findings to GitHub issues.Triggers: PR review, pull request review, scope validation, requirement compliance,backlog triage, code review, blocking issuesUse when: reviewing PRs, validating against requirements, triaging findingsto backlog, preventing overengineeringDO 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 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.

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.

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 filesUse when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git statusshows markdown artifacts that shouldn't be committed, preparing PR and needto clean up working artifacts, preserving insights from code reviewsDO 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.

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

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.

Session-aware usage logging for audit trails, cost tracking, and analytics with JSONL format.Triggers: usage logging, audit trails, cost tracking, session logging, analytics, structured logging, JSONLUse when: implementing audit trails, tracking costs, collecting usage analytics, managing session loggingDO NOT use when: simple operations without logging needs.Consult this skill when implementing usage logging and audit trails.

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.

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.

Reusable patterns and templates for Claude Code skill and hook development.Triggers: validation patterns, error handling, testing templates, workflow patterns,shared patterns, reusable templates, DRY patterns, common workflowsUse when: creating new skills or hooks that need consistent patterns, implementingvalidation logic, setting up error handling, creating test scaffolding,referencing standard workflow structuresDO NOT use when: pattern is specific to one skill only.DO NOT use when: pattern is still evolving - wait for stability.DO NOT use when: pattern is context-dependent requiring variations.Reference these patterns to validate consistency across the ecosystem.

Python testing with pytest, fixtures, mocking, and TDD workflows.Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage,test-driven development, testing patterns, parameterized testsUse when: writing unit tests, setting up test suites, implementing TDD,configuring pytest, creating fixtures, async testingDO NOT use when: evaluating test quality - use pensive:test-review instead.DO NOT use when: infrastructure test config - use leyline:pytest-config.Consult this skill for Python testing implementation and patterns.

Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.