'lean' 검색 결과

PR マージ後のローカル後片付け（worktree / ブランチ / tmux セッションの削除と main の最新化）を、収集 → 計画提示 → 承認 → 実行 → 検証のゲートで定型化する。`/post-merge-cleanup [PR番号|ブランチ名]...` の明示実行専用。

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

Execute a bounded ClawJS/Clawix code hygiene cleanup campaign from an audit report, one category and repo at a time.

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

This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

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

Creates and reviews agent skills safely by enforcing deletion-prevention harness rules: no fixed absolute temp paths, no cwd-dependent cleanup, no wildcard deletes, no workspace-external file operations, no silent cleanup failures, and mandatory temp-root validation before any destructive command. Use when creating a new skill, updating an existing SKILL.md, or reviewing prompts/runbooks that include temp files, extraction, cleanup, PowerShell, bash, rm, del, Remove-Item, or archive expansion.

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

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...

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

Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.

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

Clean architecture v3 — use cases, entities, interfaces, dependency inversion, testing, boundaries

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

Expert en clean architecture (use cases, entities, interface adapters, dependency inversion)

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

Clean up git worktrees across your repos: list every worktree, classify it as merged, remote-only, local-only or dirty, recap what each holds, and remove only the merged clean ones after GO. Use for "clean up worktrees", "what is in my aos-wt folders", "land my worktrees", "prune worktrees".

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

This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."

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

Runs a comprehensive 20-point code quality audit on a "vibe-coded" codebase that was shipped fast and now needs hardening. Use this skill whenever the user mentions vibe coding, vibe audit, code audit, code review, code cleanup, hardening a prototype, productionizing a codebase, technical debt cleanup, or asks Claude to "audit my code", "review my codebase", "clean up my project", or check a freshly-shipped project for common quality issues. Also use when a user shares a repo and asks what's wrong with it or how to make it production-ready.

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

Use to create, update or verify the Lean 4 executable specification under lean/ from the exploration documents (event-timeline, hotspots, ubiquitous-language, ux-review, model-review) — initial generation, reflecting a session's results, fixing lake build, adding a command or a screen, checking a proposed feature against the model. Formalization questions go to model-review.md as MQ, never to the expert directly.

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

Use when you need the current position in the Lean spec-driven pipeline, or any deterministic check of a Cradle project — status, golden regression, Lean layer walls, regeneration impact, unslop lint, ddd cleanup. Runs the scripts under scripts/ and reports their output verbatim.

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

Build AI data cleaning systems. TRIGGERS - Use when user needs help with ai-data-cleaner related tasks.

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

Quality control for flow, spectral, and mass cytometry - time-based anomaly cleaning (flowAI, flowCut, PeacoQC, flowClean), margin/boundary event removal, signal-drift detection, dead-cell exclusion, CyTOF Gaussian/DNA/event-length checks, instrument calibration/standardization (MESF, CS&T, peak-2), and batch-level outlier flagging. Use when assessing acquisition quality, choosing a cleaning tool, ordering QC relative to compensation, deciding margin removal before density-based steps, or flagging problematic samples before clustering or differential analysis.

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

Clean up git branches marked as [gone] (deleted on remote but still exist locally). Use when you want to prune stale local branches, remove worktrees for deleted branches, or clean up after PR merges.

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

Pick the right business-model canvas (Lean Canvas, Business Model Canvas, or Value Proposition Canvas) for the stage and fill it with specifics — one segment, one primary canvas, top-3 assumptions, no fluff in the moat or channel boxes. Load when the user asks to fill a business model canvas, lean canvas, value proposition canvas, model this business, map the business model, says "fill the BMC", "make a Lean Canvas", "Value Proposition Canvas for this", "model this idea", "what's the business model", "design the business model". Sub-skill of `venture-exploration`. Hard-bans "everyone" segments, generic channels ("SEO/social/content/ads"), and "unfair advantage = AI/data/network effects" with no concrete asset. Does NOT score viability — for that use `idea-evaluation`.

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

Quality control for flow, spectral, and mass cytometry - time-based anomaly cleaning (flowAI, flowCut, PeacoQC, flowClean), margin/boundary event removal, signal-drift detection, dead-cell exclusion, CyTOF Gaussian/DNA/event-length checks, instrument calibration/standardization (MESF, CS&T, peak-2), and batch-level outlier flagging. Use when assessing acquisition quality, choosing a cleaning tool, ordering QC relative to compensation, deciding margin removal before density-based steps, or flagging problematic samples before clustering or differential analysis.

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

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

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

Clean Architecture knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for Clean Architecture and Hexagonal Architecture audits.

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

Credit risk data cleaning and variable screening pipeline for pre-loan modeling. Use when working with raw credit data that needs quality assessment, missing value analysis, or variable selection before modeling. it covers data loading and formatting, abnormal period filtering, missing rate calculation, high-missing variable removal,low-IV variable filtering, high-PSI variable removal, Null Importance denoising, high-correlation variable removal, and cleaning report generation. Applicable scenarios arecredit risk data cleaning, variable screening, pre-loan modeling preprocessing.

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

OpenClaw 테스트의 메모리 증가와 부족 원인을 조사합니다. 측정값과 메모리 객체 기록을 비교해 실제 해제 누락과 테스트 프로세스의 모듈 보존을 구분하고 수정 결과를 검증합니다.

• Vitest 메모리 부족 원인을 조사합니다
• 같은 프로세스의 메모리 기록을 비교합니다
• 해제 누락과 모듈 보존을 구분합니다

구현이 끝나면 전체 테스트를 확인하고 로컬 병합, 풀 리퀘스트 생성, 현상 유지 중 선택한 작업을 수행합니다. 선택과 작업 환경에 따라 브랜치와 작업 공간을 정리합니다.

• 완성한 기능을 로컬에서 병합
• 브랜치를 푸시하고 풀 리퀘스트 생성
• 완료한 변경을 나중에 통합하도록 보관

Claude Code에서 Git 푸시와 변경 사항 폐기 등을 실행 전에 차단하는 훅을 설정합니다. 프로젝트별 또는 전체 적용을 선택하고 차단 명령 조정과 동작 확인까지 진행합니다.

• Claude Code의 Git 푸시 차단
• 변경 사항 폐기와 브랜치 삭제 방지
• 프로젝트별 또는 전체 제한 설정