'maintenance' 검색 결과

Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.

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

Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.

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

Build or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".

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

監督・管理者が、提出された工程進捗と日報を承認・修正承認・差戻しし、KY・ヒヤリハット・ナレッジ・日報の記録をメンテナンス（修正・ナレッジ化）する。承認した進捗は 3D に反映される。Use when: 承認, 差戻し, 確認待ち, レビュー, 監督確認, 修正して承認, 記録の修正, メンテナンス, ナレッジ化

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

Vygotsky's Zone of Proximal Development and scaffolding as a working framework for learning support. Covers the ZPD definition, the distinction between independent and assisted performance, the six scaffolding functions (recruitment, reduction in degrees of freedom, direction maintenance, marking critical features, frustration control, demonstration), fading, sociocultural mediation, and the relationship between ZPD and deliberate practice. Use when deciding how much help to give, designing collaborative learning, or assessing a learner's ceiling rather than just their current floor.

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

Meta-cognitive and practical strategies for learning any language -- learner autonomy, goal setting, strategy taxonomy (Oxford's SILL framework), memory strategies, cognitive strategies (note-taking, summarizing, analyzing, reasoning), compensation strategies, metacognitive strategies (planning, monitoring, evaluating), affective strategies (managing anxiety, self-encouragement), social strategies (collaboration, questioning, empathy), immersion design, study habit optimization, plateau diagnosis, and motivation maintenance. Use when designing a language learning plan, diagnosing a learner's stuck points, selecting study methods, or building self-directed learning skills.

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

Guidance for writing OpenStack operations manual procedures following NASA document standards. Use when authoring per-service procedures, maintenance workflows, or operational documentation that must be verified against running infrastructure.

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

Guides pytest test architecture for Python 3.11+ using behavioral contracts, risk, and maintenance-adjusted value. Use when choosing unit/integration/property/e2e boundaries, fixture strategy, coverage measurement, or mutation testing. Preserves existing project gates but does not invent test-pyramid ratios, coverage percentages, mutation-score targets, or tests for implementation detail.

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

Use when the user asks for a read-only, actionable audit of Python code quality, modernization, maintenance burden, ecosystem opportunities, or Pythonic design across a PR, git diff, staged/unstaged changes, files, or directories.

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

Use when independently hunting Python code smells, deviations from engineering standards, maintenance hazards, or suspicious design choices in a bounded review surface.

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

Follow up on open PRs in skillsaw — fix failing CI, address reviewer feedback, push updates, and validate backward compatibility. Use when an open PR needs maintenance.

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

Read-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.

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

Use when editing Qwik's .ruler guidance, adding or changing rules or skills, keeping AI guidance from going stale, updating assistant setup docs, or answering how Ruler should generate assistant-native guidance, skills, config, or policy for this repo.

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

Evaluate or operate DuckLake on MotherDuck when open table formats, bucket ownership, or file maintenance matter.

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

Maintain go-authcrunch Make targets, pinned Go tools, build/test orchestration, maintenance scripts, generated artifacts, and embedded UI refresh workflows.

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

Use GitHub Agentic Workflows to let an agent triage issues, inspect CI failures, or deliver scheduled repository upkeep inside GitHub Actions with explicit workflow definitions and reviewable runs. This is for bounded, repeatable repository operations, not for listing GitHub as a general coding platform.

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

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

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

Tracks infrastructure asset performance with maintenance planning, capital expenditure optimization, and end-of-life valuation. Use when managing infrastructure portfolios, planning capex, or evaluating asset condition.

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

Reddit account cultivation for indie developers. Uses AppleScript to control real Chrome — undetectable by anti-bot systems. Checks karma, finds rising posts, drafts comments, and posts directly. Triggers on "/reddit-cultivate", "check my reddit", "reddit maintenance", "find reddit opportunities", "build reddit karma".

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

Find and fix broken internal links, dead external URLs, stale imports, missing cross-references, and orphaned files. Ensures all project references remain valid and up-to-date. Use when documentation contains broken internal links, external URLs return 404 errors, import statements reference moved or deleted modules, cross-references between files are out of sync, or files exist but are never referenced anywhere in the project. Also use in index mode for a directory of markdown notes with a designated index, such as an agent-memory store, where an orphan is a file the index does not link to.

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

Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private research repo for public reference.

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

Maintain the 8 essential garden hand tools through sharpening, handle care, rust prevention, and seasonal storage. Covers bypass secateurs, hori-hori, hand fork, trowel, pruning saw, sharpening stone, watering can, and soil rake. Use after each garden session for quick cleaning, monthly during the growing season for sharpening and oiling, at end of season for winter storage preparation, before spring for pre-season readiness checks, or whenever a tool feels dull, stiff, or shows rust.

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

Organize, extract, prune, and verify Claude Code persistent memory files. Covers MEMORY.md as a concise index, topic extraction to dedicated files, staleness detection, accuracy verification against project state, the dual 200-line / 25KB load cap, and reachability of topic files from the index. Use when MEMORY.md is approaching either load cap, after a session produces durable insights worth preserving, when a topic section has grown beyond 10-15 lines and should be extracted, when project state has changed and memory entries may be stale, or before and after rewriting the index so that no topic file loses its only pointer.

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

AI self-healing through systematic subsystem assessment, rebalancing, and integration. Maps healing modalities to AI-internal processes: memory foundation, reasoning clarity, tool use accuracy, communication alignment, and creative coherence. Covers assessment triage, subsystem scanning, drift correction, and memory integration. Use mid-session when responses feel formulaic or disconnected, after a chain of errors suggesting subsystem drift, when context overload may have staled earlier assumptions, or as proactive maintenance between complex tasks.

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