Tools & Utilities
Essential command-line tools and system utilities.
release-please-protection
Detects and prevents manual edits to release-please managed files (CHANGELOG.md, version fields in package.json, pyproject.toml, Cargo.toml). Provides conventional commit templates. Use when editing changelogs, version bumps, release files, or when user mentions "release", "changelog", "version bump", or "conventional commits".
git-log-history
Queries Git history/logs. Use for commits/diffs/blame. Triggers - audits, reviews.
git-commit
Stage meaningful diffs and create commits with WHY-focused messages. Use when agent needs to commit code changes.
semantic-commit
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.
git-workflow
Route ALL git operations to appropriate resources. Load reference files before responding. Scope: status, diff, log, commits, branches, conflicts, rebasing, code review. Triggers: "git", "status", "diff", "log", "commit", "branch", "merge", "conflict", "rebase", "stash", "cherry-pick".
conventional-commits
Format git commit messages following Conventional Commits 1.0.0 specification. Use when the user asks to commit changes, create a git commit, or mentions committing code. Ensures consistent, semantic commit messages that support automated changelog generation and semantic versioning.
managing-dotfiles
Use this skill when working with dotfiles managed by yadm. This includes pulling remote changes, committing and pushing dotfile changes, modifying configuration files (shell, editor, terminal, git, etc.), viewing tracked files, resolving merge conflicts, and maintaining the dotfiles repository.
git-repo-analysis
Analyze git repositories and generate comprehensive markdown documentation for quick understanding. Use when user asks to "analyze this repo", "document the codebase", "explain how this project works", "generate repo docs", "understand this codebase", or wants documentation about project architecture and modules. Triggers on requests for codebase analysis, architecture documentation, module documentation, or project understanding.
codereview
codereview / code review / 代码审查 - Go 代码深度审查技能，专注于性能、安全性、并发安全和可读性。支持审查本地未提交代码、最近 commit 或指定的 commit/分支/tag。支持简洁/详细两种输出模式。
monitoring
Game server monitoring with metrics, alerting, and performance tracking for production reliability
structured-logging
Apply structured logging best practices using Pino for Node.js applications: JSON output, log levels, context, redaction, correlation IDs, and centralization. Use when implementing logging, reviewing log statements, or discussing observability.
monitoring-skill
Monitoring and observability with Prometheus, Grafana, ELK Stack, and distributed tracing.
debug-logs
Structured debugging workflow with log server capture and analysis
code-examples
Find real-world code examples across millions of GitHub repositories. Use when the user wants to see how others implement something, find usage patterns, or discover code examples in the wild.
testing-assistant
Activates when user needs help writing tests, understanding testing patterns, or improving test coverage. Triggers on "write tests", "add unit tests", "test this function", "improve coverage", "mock this", "testing strategy", or questions about Jest, pytest, testing frameworks.
code-review-checklist
Code review guidelines covering code quality, security, and best practices.
permissions
Manage ekkOS tool permissions. View, grant, or revoke permissions for proactive tool execution. Use when user types "/permissions" or wants to configure what ekkOS can do automatically.
skillstash-author
Author skillstash SKILL.md files from research or issue specs
fact-checking
Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these claims accurate".
fact-checker
Validate changes for factual accuracy, completeness, and intent preservation without modifications. Scope: fact-checking, verifying refactors, validating imports, checking rewrites, comparing versions, reviewing documentation changes. Triggers: "fact-check", "verify", "validate", "compare versions".
doc-quality
Review and improve documentation quality using best practices. Use when reviewing changelogs, documentation, or any written content to ensure clarity, accuracy, and helpfulness.
