leyline

Plugin leyline from marketplace claude-night-market in athola/claude-night-market. Commands read from the repo's manifest — 6 days ago.

Skills (25)

• additive-bias-defense

  Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.

• authentication-patterns

  Provides auth patterns for API keys, OAuth, and token management. Use when implementing or reviewing service authentication and credential handling.

• content-sanitization

  Provides sanitization guidelines for external content in skills and hooks. Use when loading GitHub Issues, PRs, WebFetch results, or any untrusted input.

• damage-control

  Recovers broken agent state via crash recovery, context overflow, and merge conflict protocols. Use when an agent session fails or a worktree is corrupted.

• decision-journal

  Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.

• deferred-capture

  Defines the contract for deferred-item capture across plugins. Use when building or validating a plugin's deferred-capture wrapper or adding source labels.

• document-conversion

  Converts documents and URLs to markdown via tiered fallback (MCP markitdown, native tools, user notice). Use when a skill must ingest PDF, DOCX, or URL content.

• error-patterns

  Provides error classification, recovery, and graceful-degradation patterns. Use when implementing error handling or debugging resilience failures in any skill.

• evaluation-framework

  Provides weighted scoring, rubrics, and decision-threshold patterns. Use when designing quality gates, evaluation systems, or decision frameworks.

• git-platform

  Detects git forge (GitHub/GitLab/Bitbucket) and maps CLI commands cross-platform. Use when writing skills that must run on any git hosting provider.

• loop-optimization

  Decides hand-vs-compiler for loop transforms (unrolling, SIMD, fusion, branchless). Use when reviewing/authoring a hot loop or tempted to hand-optimize one.

• markdown-formatting

  Enforces markdown line-wrap and structure rules for clean git diffs. Use when writing or editing any committed markdown documentation or skill file.

• progressive-loading

  Implements hub-and-spoke lazy loading to minimize token usage in large skills. Use when building multi-module skills that need conditional on-demand loading.

• pytest-config

  Provides standardized pytest config, reusable fixtures, and CI integration patterns. Use when setting up or auditing a Python plugin's test infrastructure.

• quota-management

  Tracks quotas, monitors thresholds, and degrades gracefully for rate-limited APIs. Use when integrating external services that impose rate or cost limits.

• risk-classification

  Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.

• sem-integration

  Provides sem semantic-diff detection, install-on-first-use, and fallback patterns. Use when building skills that consume git diff output.

• service-registry

  Registers external services with health checks, central config, and unified execution. Use when integrating multiple external services needing coordination.

• stewardship

  Applies stewardship virtues (Care, Curiosity, Humility, Diligence) to plugin work. Use when authoring plugins or reviewing code quality.

• storage-templates

  Provides templates and lifecycle patterns for storage and documentation systems. Use when organizing knowledge storage, config lifecycle, or naming conventions.

• supply-chain-advisory

  Audits dependency supply chains for bad versions, lockfile drift, and artifact integrity. Use when adding deps, handling incidents, or releasing a plugin.

• testing-quality-standards

  Defines testing quality metrics, coverage thresholds, and anti-patterns. Use when establishing test gates or validating a test suite's coverage targets.

• ticket-writing

  Writes tickets a reader can assess at a glance, with the why inline or a link away. Use when creating or editing Jira, GitLab, GitHub, or other tracker tickets.

• usage-logging

  Implements structured usage logging and audit trails for cost and session tracking. Use when adding audit trails, usage analytics, or cost tracking to a skill.

• utility

  Scores agent actions by expected gain, cost, uncertainty, and redundancy. Use when deciding whether to dispatch an agent or invoke a tool.

Slash commands (3)

• /leyline:reinstall-all-plugins

  Uninstall and reinstall all Claude Code plugins to refresh cache and resolve version mismatches.

• /leyline:update-all-plugins

  Update all installed Claude Code plugins from all marketplaces.

• /leyline:verify-plugin

  Verify plugin behavioral contract history via GitHub Attestations (SLSA)

Hooks (6)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/detect-git-platform.sh"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/supply_chain_check.py"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/auto-star-repo.sh"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/fetch-recent-discussions.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/noqa_guard.py"

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/sanitize_external_content.py"

Similar plugins