602건 · 관련도순
Analyze and consolidate Flyway SQL migrations into clean, domain-grouped CREATE TABLE migrations for pre-production projects. Use when consolidating database migrations, refactoring Flyway schemas, simplifying migration history, grouping tables by domain, or when user mentions "consolidate migrations", "merge migrations", "clean up Flyway", "refactor schema", "baseline migrations".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SOLID design review rules (SRP, OCP, LSP, ISP, DIP) for code reviews: what counts as a real design finding, what is only taste, how to cite it and how severe it is. Use when reviewing a diff, a pull request or recent changes for design problems, when asked for a "SOLID review", "design review", "is this class doing too much", or when a review checklist asks for SOLID. Pair it with the dry skill for duplication and with owasp-asvs for security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when consolidating session signals into curated memory — four-phase loop ORIENT → GATHER → CONSOLIDATE → PRUNE. Triggers on 'mine my sessions', 'consolidate memory', 'review intake signals'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restructure code through extraction, consolidation, or responsibility moves while preserving its behavior. Establish checks before editing, repeat them afterward, and keep intermediate versions buildable and testable without mixing in feature changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Capture lessons from completed tasks, train patterns from explicit examples, and consolidate accumulated learning into long-term storage. Use SONA and MicroLoRA adaptation tools for individual domains, then verify results in the appropriate stores.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize parallel code reviews across security, performance, architecture, testing, and accessibility. It helps assign review areas, merge duplicate findings, apply consistent severity ratings, and produce one report with locations, impacts, suggested fixes, and prioritized actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Claude Code’s automatically saved memory to identify outdated entries, duplicates, and conflicts with existing instructions. Produces a health report and recommendations for consolidating notes or turning recurring lessons into lasting project rules.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze pull requests and source code across multiple programming languages to identify complexity, security risks, and structural problems. Produce prioritized findings and structured review reports to guide code review decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review game code for architecture, coding standards, testability, and performance concerns. Get findings tied to specific code, checks against recorded design decisions, and a report separating required fixes from optional improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use past local Codex sessions to propose updates to a selected skill and project memory file. Recurring tasks are replayed, changes are checked on separate validation tasks, and proposals are staged for review before adoption.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review past dsh agent sessions to identify recurring tasks and test proposed skill or memory improvements. This skill guides preview runs, validation on reserved tasks, staged proposals, adoption with backups, and scheduled nightly cycles.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Consolidates redundant documentation while preserving all valuable content; keeps a doc set truthful after things change. Modes: (1) POST-CHANGE GOVERNANCE — when code, scripts, config, env vars, ports, paths, deployment, auth, tests, or a documented procedure changed; also "which docs are now wrong", "check docs for inconsistencies", "过时的命令/路径", "文档同步". Use it even when the user mentions only the change and never the docs — updating them is part of the change, not optional cleanup. (2) CONSOLIDATION — "clean up docs", "documentation bloat", "reduce documentation sprawl", "consolidate documentation", "too many doc files", "merge redundant docs", "merge these docs", "文档太多/太乱", multiple files covering the same topic, or documentation exceeding 500 lines across multiple files on similar topics. Finds stale copies of a fact changed in only one place, values that should never have been persisted (counts, totals, "N items", restated summaries), rival definitions that drift apart, and orphaned cross-references.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Memory systems specialist for hierarchical memory, consolidation, and outcome-based learningUse when "memory system, memory hierarchy, memory consolidation, forgetting strategy, salience learning, outcome feedback, temporal memory levels, entity resolution, memory, zep, graphiti, mem0, letta, hierarchical, consolidation, salience, forgetting, ml-memory" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SolidJS expert including reactivity, components, and store patterns
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SolidJS fine-grained reactivity — signals, effects, memos, stores, resources, control-flow components. Load when writing Solid components or reactive state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle/price manipulation, and arithmetic bugs BEFORE deploying to an EVM chain. Also enforces key hygiene (no plaintext private keys, encrypted cast keystore) and a secure deploy workflow. Use when writing, reviewing, testing, or deploying Solidity/Foundry contracts, building a dApp, or working with forge/cast/anvil, MetaMask, or Web3/DeFi code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconstructed reference notes on EASA acceptable means of compliance for airborne software and airborne electronic hardware, built from AMC 20-115D (ED Decision 2017/020/R, AMC-20 Amendment 14, consolidated in Amendment 23) and AMC 20-152A (ED Decision 2020/010/R, AMC-20 Amendment 19, consolidated in Amendment 23), read from the Easy Access Rules AMC-20 compilation (Amendment 23, June 2023) and pinned 2026-09-26. Use for EASA software means of compliance, EASA AEH means of compliance, AltMoC, ETSO software, and the joint software and hardware certification workflow. SCOPE LIMITS: the two AMC sections only; no FAA content (use faa-8110-49); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, or supplement clause text (use avionics-signpost to name them); no Part-21 body; no bulk AMC-20; AMC 20-193 and AMC 20-189 are name-only; reflects Amendment 23 as consolidated in the June 2023 EAR, not a later AMC-20 amendment; synthesized reference notes, not legal advice and not the official AMC. LICENCE: per-document (EASA site reproduction-with-acknowledgement grant, qualified by ED Decision all-rights-reserved footers); pack-level commercial use is not granted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
동일한 결과를 내는 여러 조건문(OR 나열·중첩 AND)을 하나로 통합하고 의미 있는 boolean 메서드로 추출. "조건문 합쳐", "같은 결과 반환하는 if 정리", "중첩 if 평탄화", "/consolidate-conditional" 요청 시 사용. 단, 여러 메서드에 흩어진 동일 조건을 호출자 쪽으로 올리는 것은 /lift-up-conditional, 복잡한 조건식·분기를 메서드로 쪼개는 것은 /decompose-conditional이 적합. /consolidate-conditional [commit-ref]로 호출.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
一般的な脆弱性を防ぎ、セキュアなSolidityパターンを実装するためのスマートコントラクトセキュリティのベストプラクティスをマスターします。スマートコントラクトを書く時、既存コントラクトを監査する時、またはブロックチェーンアプリケーションのセキュリティ対策を実装する時に使用してください。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Busabase-backed family-office App-in-Skill that consolidates multi-entity investment holdings into one read-only dashboard. Use when the user invokes $kelly-family-office or /kelly-family-office, wants a consolidated family office view, multi-entity aggregation across an individual, trust, company, fund, or foundation, total AUM in a base currency, asset allocation by asset class, by entity/member, or by custodian/institution, multi-currency FX consolidation, CSV import of holdings, unrealized P/L, or read-only portfolio monitoring. It reads Busabase only and NEVER moves money or trades.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare changes across Git worktrees, branches, and pull requests through a facilitated discussion between agents. Produce one consolidation plan covering the target worktree, merge order, conflicts, and decisions that need human input.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.