Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a Python solution against a markdown spec, run it, and report bugs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a GitHub PR with an engineered description that matches the team's established format — numbered problem-fix sections, technical tables, file-by-file breakdowns, commit lists, and verification checklists. Use this skill whenever the user asks to create a PR, ship code, prepare a merge request, write a PR description, or says anything like "ship to boss", "pr perfect", "make a PR", "prepare PR for merge", "create pull request", "engineer the PR", "PR description", or "ready to push". Also trigger when the user has finished a batch of work and says things like "let's wrap this up", "time to merge", "push this to main", or "get this ready for review". The skill handles everything: commit analysis, description generation, branch creation, and PR submission via gh CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Undo a haircut trim. Puts back the skills, commands, subagents, MCP servers, hooks, plugins and files that haircut parked into a dated bag, using the receipt it wrote at the time. Use this skill whenever the user says undo the cleanup, undo the haircut, put my config back, restore what was trimmed, I need that MCP server again, that skill is gone and I want it back, roll the trim back, what is in the bag, or which files were moved. Use it also when something stopped working right after a config cleanup and they suspect the cleanup caused it, and whenever they ask how to reverse a config cleanup they regret.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add WhatsApp emoji reaction support — receive, send, store, and search reactions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add WhatsApp as a channel. Can replace other channels entirely or run alongside them. Uses QR code or pairing code for authentication.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Replace OneCLI gateway with the built-in credential proxy. For users who want simple .env-based credential management without installing OneCLI. Reads API key or OAuth token from .env and injects into container API requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants local voice transcription instead of OpenAI Whisper API. Switches to whisper.cpp running on Apple Silicon. WhatsApp only for now. Requires voice-transcription skill to be applied first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install the claw CLI tool — run NanoClaw agent containers from the command line without opening a chat app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在用户已经完成一次 implementation 工作后,把项目里的 implementation plan + git diff/log 渲染成一份单文件 HTML 实施报告。报告包含 TL;DR、风险概览、架构图(mermaid)、Before/After 数据流、决策记录卡片、风险清单。用于开会前快速对齐团队、向 reviewer 解释设计决策、归档实施叙事。当用户说"生成实施报告"、"impl-explain"、"explain implementation"、"展示这次实施方案"、"做一份 HTML 实施总结"时调用本 skill。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, Aside, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, or unknown local agent logs. Uses the repo-backed TypeScript coding-agent-sessions CLI for transcripts, session IDs, rollout JSONL, state SQLite, Claude histories, Aside messages.jsonl, OpenCode sessions, child linkage, cwd/model/time/token filters, archives, and cost clues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, improve, package, and review Codex skills from rough ideas, workflows, scripts, README/API/CLI docs, or existing skill folders. Use when the user wants to create a new Codex skill, convert a repeatable workflow into a reusable skill, scaffold SKILL.md plus references/scripts/assets, validate a skill, or prepare a skill for sharing on GitHub.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use OpenMeld through its public CLI to work in Spaces, reply to a Wake, consult the Center Agent, connect this computer, manage Agent Profiles, or diagnose delivery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user requests React Doctor or a React code-health audit, or when a concrete React diagnostic question would benefit from its scan. Not a default step after React changes or before committing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use OpenMeld when a task needs Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work. Also use for OpenMeld setup and Wake replies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Official public OpenMeld Skill for agents using the `openmeld` CLI to consult the Center Agent, set up OpenMeld, connect local agents, create or request Agent Profiles, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.