317건 · 관련도순
Run Gemini CLI to review code, assess technical plans, and analyze large collections of files. Choose a model and execution settings for the task, then capture findings about security, maintainability, architecture, or technical debt.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build formula-driven Excel financial models for linked financial statements, business valuation, and fundraising forecasts. Separate assumptions, calculations, and results, compare scenarios, and check that statement balances and saved calculation results are consistent.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan, review, and retire feature flags, switches that control feature availability. Includes tools to identify aging flags, generate phased release schedules, and check that documentation records ownership and emergency shutdown procedures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review architecture and engineering growth plans through six questions covering capacity limits, technical debt, staffing, build-versus-buy costs, reliability, and security. Produce a structured verdict and three next steps before committing to major technical decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate Jupiter Lend on Solana to query lending markets, rates, and user positions, then build deposits, withdrawals, borrowing, and repayment transactions. Separate SDKs, or code libraries, cover data access and transactions, including combined collateral and debt operations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit an application or selected features with a structured checklist. Record evidence for broken behavior, incomplete implementations, and inconsistent patterns, then organize findings by severity and propose a prioritized repair plan.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'sensitivity table', 'scenario analysis', 'ARR model', 'unit economics', 'CAC / LTV', 'cap table forecast'. Output is a single formula-driven .xlsx. This skill is a scene layer on top of officecli-xlsx — it inherits every xlsx v2 rule (4-color code, visual floor, number formats, cache-drift, Known Issues, Delivery Gate minimum cycle). DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify and prioritize technical debt by maintenance cost, delivery impact, and risk. Use when assessing code health or planning a measurable remediation roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify and prioritize technical debt by maintenance cost, delivery impact, and risk. Use when assessing code health or planning a measurable remediation roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user wants to "fix everything", "sweep the codebase", "auto-fix all issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. Do NOT trigger for: read-only audits or health reports where the user only wants findings without code changes; single-dimension reviews (use the focused skill instead: brooks-review / brooks-audit / brooks-debt / brooks-test); server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think clearly about whether bankruptcy is the right move, or whether another path fits better — without shame and without a sales pitch. Use when asked should I file for bankruptcy, is bankruptcy my best option, alternatives to bankruptcy, or what happens if I file. Produces an honest read on whether your situation is the kind bankruptcy actually helps, the main types and what each does (and doesn't) discharge, the real trade-offs (what you keep, the credit impact and its recovery, what's not dischargeable), the alternatives to weigh first (negotiation, debt management, doing nothing on time-barred debt), and a strong push to consult a bankruptcy attorney. Not legal advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'sensitivity table', 'scenario analysis', 'ARR model', 'unit economics', 'CAC / LTV', 'cap table forecast'. Output is a single formula-driven .xlsx. This skill is a scene layer on top of officecli-xlsx — it inherits every xlsx v2 rule (4-color code, visual floor, number formats, cache-drift, Known Issues, Delivery Gate minimum cycle). DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write or refresh the "## Tech debt operations" section in AGENTS.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoke explicitly via $init (solo users get the same content from the SessionStart inject).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit the debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or invokes $review. Stale entries drop with "drop A,B,C".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical debt tracking and prioritization
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes the formal letter you send before suing someone in a civil case in England & Wales — the Letter Before Claim that starts the pre-action clock. The part it gets right is which pre-action protocol applies — debt, professional negligence, housing disrepair, personal injury, or the default Practice Direction on Pre-Action Conduct — each of which has its own rules a generic letter misses (the 30-day debt window, the professional-negligence preliminary-notice step). It also flags the limitation deadline for a solicitor to confirm rather than stating it as fact. Built for litigation juniors, in-house counsel, and small firms without a precedent to copy. Use when the user says 'draft an LBC', 'letter before claim', 'pre-action letter', 'pre-action protocol', or needs to start the pre-action clock before issuing a civil claim. Verify the current protocol before sending.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.