'maintenance' 검색 결과

Evolve an existing skill by refining its content in-place or creating an advanced variant. Covers assessing the current skill, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes, updating version metadata, and synchronizing the registry and cross-references. Use when a skill's procedure steps are outdated, user feedback reveals gaps, a skill needs a complexity upgrade, an advanced variant is needed alongside the original, or related skills are added and cross-references are stale.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evolve an existing agent definition by refining its persona in-place or creating an advanced variant. Covers assessing the current agent against best practices, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes to skills, tools, capabilities, and limitations, updating version metadata, and synchronizing the registry and cross-references. Use when an agent's skills list is outdated, user feedback reveals capability gaps, tool requirements have changed, an advanced variant is needed alongside the original, or the agent's scope needs sharpening after real-world use.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Remove dead code, unused imports, fix lint warnings, and normalize formatting across a codebase without changing business logic or architecture. Use when lint warnings have piled up during rapid development, unused imports and variables clutter files, dead code paths were never removed, formatting is inconsistent, or static analysis tools report fixable hygiene issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and repair Claude Code discovery symlinks for skills, agents, and teams. Compares registries against .claude/ directories at project and global levels, detects missing, broken, and extraneous symlinks, distinguishes almanac content from external projects, and optionally repairs gaps. Use after adding new skills or agents, after a repository rename or move, when slash commands stop working, or as a periodic health check.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research-backed template refresh workflow for updating existing templates with placeholder verification and rendering validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research-backed JSON Schema refresh workflow for updating existing schemas with validation checkpoints and cross-reference verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Schedule recurring tasks and heartbeat monitoring using Claude Code's cron system (CronCreate/CronList/CronDelete). Implements the Agentic Heartbeat Pattern for ecosystem health monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research-backed hook refresh workflow for updating existing hooks with TDD checkpoints and settings.json registration validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when source-backed project knowledge needs to be created, refreshed, or corrected.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when contradictions, revisit conditions, or duplicates appear in knowledge entries. Not for remote, credential, publish, deploy, or irreversible changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a proof needs Rocq (formerly Coq), including legacy Coq codebase maintenance and migration through the Coq to Rocq rename. Not for Lean 4: use writing-lean-proofs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when schema-governance contracts or related Odylith registry truth need maintenance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use after source-of-truth changes when Odylith delivery or governance surfaces need maintenance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Independently attempt to falsify one Proto UI autonomous-maintenance finding in a fresh non-mutating context. Use after pui-observe produced a candidate finding and route the result directly to remediation or closure when authority is clear.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Repair one independently verified Proto UI maintenance finding when governing authority or an explicit product decision fixes the expected result. Use for the bounded remediation and its evidence packet before independent review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Freeze one eligible Proto UI autonomous-maintenance candidate into a bounded mission packet and lease. Use before observation when a current request or governed queue supplies scope, oracle, baseline, capability, risk, budget, completion, and stop conditions. Do not observe, verify, repair, or invent a mission.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Route ordinary Proto UI development through a minimal composition of repository skills. Use when starting, continuing, or handing off feature, fix, spec, contract, Module, Host Capability, Adapter, Prototype, component, test, documentation, review, or release-preparation work. Do not use for autonomous-maintenance runs; use pui-maintain.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Record one authorized non-remediation terminal outcome in Proto UI's autonomous-maintenance state. Use after a supported no-finding result, an independently rejected finding, or a blocked mission whose terminal evidence is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Periodic housekeeping and session lifecycle management. Use when performing cleanup, pruning, or session commands.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find authoritative guidance for installing, configuring, operating, securing, and troubleshooting OpenClaw, including channels, model providers, Gateway operations, tools, plugins, automation, nodes, multi-agent routing, and CLI errors. Use for any question or maintenance task involving an OpenClaw installation, `openclaw` CLI command, Gateway daemon, configuration key, or integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Health-check a persistent markdown wiki. Use this when the user wants to find orphan notes, dangling links, missing pages, graph gaps, contradictions to review, or general wiki maintenance opportunities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.