Claude Skills by majiayu000

Use when creating llmring.lock file for new project (REQUIRED for all applications), configuring model aliases with semantic task-based names, managing environment-specific profiles (dev/staging/prod), or setting up fallback models - lockfile creation is mandatory first step, bundled lockfile is only for llmring tools

Use Lockplane for safe database schema management - define schemas in .lp.sql files, validate, and apply with shadow DB testing

Author or update Locque .lq code and tests with the canonical M-expr syntax, CBPV rules, data/match forms, modules/imports/opens, and project conventions.

Record agent run logs into .tmp/logs/. Use this to maintain an audit trail of agent actions and errors.

Set up centralized logging with ELK, Loki, or Splunk for log management

Implement centralized logging with ELK Stack, Loki, or Splunk for log collection, parsing, storage, and analysis across infrastructure.

Execute PowerShell commands on Windows systems with security constraints

Fast log file analysis with lnav, multi-framework support (Laravel, CodeIgniter, React, Next.js), automatic log pruning, and 70-80% token savings vs reading entire logs

Analyze application and system logs to identify errors, patterns, and root causes. Use log aggregation tools and structured logging for effective debugging.

Generate and execute Python code to analyze large log datasets, detect patterns, and extract actionable insights

Parse and analyze system and application logs. Use when the user says "find errors in logs", "analyze logs", "check journalctl", "what's in the logs", "debug from logs", or asks to investigate log files.

解析和分析日志文件，支持模式匹配、过滤、统计和错误检测。

Archives completed logs to cloud storage with index management and cleanup

Log a coding problem attempt when user says "log <problem_id>" with time, tries, solved status, hints, or solution usage. Parses natural language like "log count_bits - 15 min, 3 tries, solved" and calls the log-attempt script.

Audit logs in project against fractary-logs best practices and generate actionable remediation specification

Run /check-bitcoin, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-bitcoin instead if you want to fix issues immediately.

Captures Claude Code conversation sessions in structured markdown format tied to work items with redaction

Classifies logs by type (session, test, build) using path patterns and frontmatter analysis

Log problems, bugs, and debugging processes with solutions. Use when encountering issues during development, debugging problems, or documenting solutions for future reference. Maintains DEBUG_LOG.md with structured problem-solution entries.

Orchestrates multi-log workflows with parallel execution for batch operations across many logs

Run /check-docs, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-docs instead if you want to fix issues immediately.

When a mode needs to read, create, or write (log progress) to a log file.

Analyze system, application, and security logs for forensic investigation. Use when investigating security incidents, insider threats, system compromises, or any scenario requiring analysis of log data. Supports Windows Event Logs, Syslog, web server logs, and application-specific log formats.

Run /check-landing, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-landing instead if you want to fix issues immediately.

Log key learnings to progress.txt during PRD iteration. Use when you discover codebase patterns, encounter gotchas, make important decisions, or learn something that would help future work sessions. Triggers on: log learning, add to progress, capture insight, record pattern, note gotcha, save lesson.

Lists and filters logs by type, status, date range, and work item with frontmatter parsing

Orchestrates single-log sequential workflows by coordinating operation skills for individual logs

Reads and analyzes application logs for debugging and monitoring.

Run /check-observability, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-observability instead if you want to fix issues immediately.

Parses log files to identify errors and self-correction attempts.

Run /check-product-standards, then create GitHub issues for all findings. Invoked by /groom as P1 fundamental check.

Read MetaTrader 5 log files. TRIGGERS - MT5 logs, Experts pane, indicator errors, compilation errors.

Inspect error logs quickly; use when log snippets or stack traces are mentioned.

Searches logs by content keywords, patterns, and filters with context extraction

Log entries to the current learning session. Use mid-session to save progress, capture concepts learned, or record corrections. Triggers on "log this", "save progress", "record what we learned".

记录执行过程的 Skill。当需要保存执行记录、工作日志时触发。触发词：记录、log、日志、work log、保存记录。

Run /check-stripe, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-stripe instead if you want to fix issues immediately.

This skill provides guidance for analyzing log files across date ranges and producing summary statistics. Use when tasks involve parsing log files, counting log entries by severity (ERROR, WARNING, INFO), aggregating by date ranges (today, last N days, month-to-date), or producing CSV reports from log data.

Validates logs against type-specific schemas checking frontmatter, structure, and required fields

View and analyze WaveCap-SDR server logs, debug output, and error messages. Use when troubleshooting server issues, debugging API errors, monitoring SDR device status, or investigating capture/channel problems.

Run /check-virality, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-virality instead if you want to fix issues immediately.

Log the work segment that you did after the last work log until now in a

Creates or updates logs using type-specific templates with automatic validation and formatting

RFC-27 compliant static Logback configuration for Java services. Covers logback.xml structure, appenders, encoders, and deployment-specific configuration. Use when setting up or reviewing logging configuration in Java services.

Writes user-friendly logger messages in active voice for Simple History event logs. Fixes passive voice issues. Use when creating or modifying logger classes in loggers/ directory, writing getInfo() messages, fixing passive voice, reviewing log message clarity, or adding new events to the activity log.

Structured logging and reporting system for development work sessions. Trigger: Completing development tasks, generating session reports, documenting changes.

Centralize logs with ELK/EFK and retention policies.

日志最佳实践，强调宽事件（canonical log lines），便于调试与分析。

Configures logging systems, log aggregation, and log analysis pipelines

实作结构化日誌，包含正确的日誌层级和敏感数据处理。 使用时机：新增日誌、除錯、设置可觀测性。 关鍵字：logging, log level, structured logging, observability, 日誌, 记录, 结构化日誌。