'debt' 검색 결과

Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.

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

Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes $metrics. Read-only, never writes the log.

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

Migrate, modernize, and upgrade codebases to AWS. Run analysis on repos for tech debt, security vulnerabilities, and modernization opportunities. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. Use when the user says "migrate .NET to AWS", "upgrade Java to 17/21", "modernize COBOL", "modernize mainframe", "move VMware to EC2", "convert SQL Server to Aurora", "upgrade Python version", "migrate AWS SDK", "transform this codebase", "analyze for issues", "find tech debt", "what tech debt", "security vulnerabilities", "CVEs", "what's wrong with my code", "assess my repos", "where do I start", "find what's outdated", "analyze my repos", "AWS Transform - continuous modernization", "continuous modernization" or "continuous-modernization". Don't use for infrastructure provisioning, CI/CD pipelines, or general coding tasks.

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

Use when reworking a change to prevent tech debt, or auditing existing debt to categorize, score, and prioritize the refactor backlog.

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

Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.

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

Keeping codebases healthy, performant, and maintainable - refactoring, performance optimization, and technical debt managementUse when "refactor, optimize, performance, technical debt, cleanup, architecture, speed up, bundle size, memory leak, slow query, code smell, complexity, dead code, performance, refactoring, optimization, technical-debt, architecture, cleanup, bundle, memory" mentioned.

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

Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.

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

Autonomous orchestrator that scans, refactors, and eradicates technical debt at the end of the development lifecycle to achieve a Zero Debt codebase / Orkestrator otonom untuk menghapus utang teknis sebelum rilis.

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

Synthesizes DCM market activity with new issue spreads, fund flows, and market technical analysis for issuance timing. Use when analyzing debt market windows, timing bond issuance, or assessing market receptivity.

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

Evaluates green bonds, sustainability-linked bonds, and social bonds with KPI selection, step-up mechanics, and framework assessment. Use when structuring ESG-linked debt, analyzing sustainability frameworks, or evaluating green bond eligibility.

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

Evaluates mezzanine structures with PIK toggle, equity kickers, and intercreditor subordination mechanics. Use when analyzing mezzanine financing, comparing subordinated debt terms, or modeling layered capital structures.

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

Evaluates target leverage capacity with cash flow coverage, stress testing, and optimal debt structure across term loans, revolver, and mezzanine. Use when analyzing debt capacity, structuring acquisition financing, or stress testing leverage.

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

Review software architecture for coupling, cohesion, SOLID principles, API design, scalability, and technical debt. Covers system-level evaluation, architecture decision record review, and improvement recommendations. Use when evaluating a proposed architecture before implementation, assessing an existing system for scalability or security, reviewing ADRs, performing a technical debt assessment, or evaluating readiness for significant scale-up.

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

Perform controlled dismantling of rigid system structures while preserving essential capabilities (imaginal discs). Covers rigidity mapping, dissolution sequencing, knowledge extraction, interface archaeology, and safe decomposition of technical debt and organizational calcification. Use when assess-form classified the system as PREPARE or CRITICAL, when a system is so calcified that incremental change is impossible, when technical debt blocks all forward progress, or before adapt-architecture when the current form must be softened before it can be reshaped.

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

Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.

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

Run a focused tech debt reduction sprint — inventories all technical debt (TODOs, outdated deps, missing tests, god objects), fixes code smells, removes dead code, then hardens with a review pass. Use when a codebase feels sluggish, before a major feature push, or on a regular maintenance cadence.

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

Drafts a Chapter 11 Plan of Reorganization under 11 U.S.C. §§ 1121–1129 with claim classification, treatment provisions, distribution mechanics, executory contract determinations, and confirmation compliance. Use when preparing reorganization plans, restructuring debts, classifying claims, drafting Chapter 11 plans, or helping debtors emerge from bankruptcy. Trigger keywords: reorganization plan, Chapter 11, plan of reorganization, debt restructuring, cramdown, claim classification, confirmation order.

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

Deep code review - Elixir idioms, OTP patterns, tech debt, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, techdebt, tech debt, code smells.

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

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

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

This skill should be used when the user asks to "recalculate debt", "利息制限法で引き直し", "引き直し計算", "過払金", "過払い金", "サラ金", "貸金業者との取引履歴から引き直し", or wants deterministic recalculation of loan transactions under the Interest Rate Restriction Act.

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

プロジェクト全体の技術負債をスキャンし、親Issueの実装範囲を基に優先度を分類する。Triggers on: '/reduce-debt', '技術負債チェック', '負債チェック'

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

Explain and list Peephole sec-debt markers — deliberate, human-authorized security trade-offs recorded in code. Use when the user says /sec-debt, wants to knowingly accept a security finding, or asks what deferred security items exist.

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

Build Excel workbooks for buyouts financed with debt. Using a supplied or standard template, the skill connects funding, operating forecasts, debt repayment, and returns, calculating IRR, an annualized return measure, and MOIC, the investment multiple.

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

• Populate an LBO template with acquisition assumptions
• Review borrowing, interest, and repayment schedules
• Calculate investment returns using IRR and MOIC

Review AI-generated code for problems hidden behind successful runs. Check failure handling, resource cleanup, unusual inputs, nonexistent dependencies, and departures from project conventions to identify missing safeguards before merging or accepting the work as complete.

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

• Audit code after an AI generation session
• Review an AI-generated pull request before merging
• Investigate brittle code that appears to work