322 个 · 按相关度排序
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
中文简介正在准备中。当前显示原文说明。
Lint and typecheck debt paydown: clear pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms. Runs on green main. For diff-scoped quality use absolute-simplify. Triggers on "absolute debt", "fix our lint warnings", "clear the type errors", "get to strict mode", "burn down suppressions".
中文简介正在准备中。当前显示原文说明。
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
中文简介正在准备中。当前显示原文说明。
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
中文简介正在准备中。当前显示原文说明。
Structures debt maturity analysis with refinancing risk, market access assumptions, and liability management opportunities. Use when analyzing maturity walls, planning refinancing, or optimizing debt tenor.
中文简介正在准备中。当前显示原文说明。
Calculates borrower debt capacity with cash flow coverage, leverage multiples, and stress-tested servicing ability. Use when sizing debt facilities, analyzing leverage capacity, or determining optimal capital structure.
中文简介正在准备中。当前显示原文说明。
Creates debt offering memoranda with credit overview, financial analysis, industry section, and risk factors for investor marketing. Use when preparing debt OMs, writing credit marketing materials, or structuring lender presentations.
中文简介正在准备中。当前显示原文说明。
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
中文简介正在准备中。当前显示原文说明。
Use when a task needs the judgment of a Credit Counselor — calculating debt-to-income ratio and disposable income to test debt management plan (DMP) feasibility, comparing DMP versus debt settlement versus bankruptcy for a specific client's financial situation, negotiating and applying creditor interest-rate concessions, selecting a debt payoff order matched to a client's follow-through pattern, or providing federally required pre-bankruptcy credit counseling.
中文简介正在准备中。当前显示原文说明。
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
中文简介正在准备中。当前显示原文说明。
Use when executing admin-level cleanup in a Salesforce org: deleting unused fields, removing inactive Flow versions, deactivating legacy automation, running Salesforce Optimizer or Org Check, and performing destructive metadata deploys. Triggers: 'clean up unused fields', 'delete inactive flows', 'run Optimizer', 'org has too many custom fields', 'remove old workflow rules', 'Flow version limit'. NOT for assessing or reporting on technical debt (use architect/technical-debt-assessment). NOT for code-level refactoring or Apex cleanup (use apex/ skills).
中文简介正在准备中。当前显示原文说明。
Durable categorized record-keeping for any predicate-enabled walk. Trigger when: - Classifying a step's output for recording (decision, finding, debt, feedback). - Promoting a scratch artifact to the ledger, to repo/docs, or to a category home (.ledger/tech-debt/, .ledger/process-feedback/). - Auditing whether a draft is structurally ready for its destination. - Running a zero-context sensibility read before committing to promotion. - Recording a known limitation as a tech-debt entry (not prose in the log). - Recording a friction, miss, improvement, or process amendment. - Prompt contains: /record, record-keeping, promote, ledger note, zettelkasten, scratch-to-ledger, zero-context read, over-strip, classification trigger, tech-debt, process-feedback, amendment.
中文简介正在准备中。当前显示原文说明。
Read-only measurement of an agent's autonomy debt from its approvals log: how many times it asked the human for permission in a window, how many asks expired unanswered, and which classes they fall into (machine noise, login or 2FA, physical UAC, money). Use to find asks the agent should have decided itself and to cut needless interruptions. Triggers: /ask-debt, autonomy debt, how often do I ask, expired asks.
中文简介正在准备中。当前显示原文说明。
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
中文简介正在准备中。当前显示原文说明。
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
中文简介正在准备中。当前显示原文说明。
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
中文简介正在准备中。当前显示原文说明。
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
中文简介正在准备中。当前显示原文说明。
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
中文简介正在准备中。当前显示原文说明。
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
中文简介正在准备中。当前显示原文说明。
Audit the project's technical health and identify "high-interest" debt. Load when the user asks to check code quality, find TODOs, assess project health, or prepare for a refactoring sprint. Also triggers on "technical debt audit", "where is the code messy", "assess project health", "find my hacks", or "identify tech debt". Essential for maintaining velocity in growing projects.
中文简介正在准备中。当前显示原文说明。
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.
中文简介正在准备中。当前显示原文说明。
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
中文简介正在准备中。当前显示原文说明。
Complete Excel templates for leveraged buyouts, acquisitions financed partly with debt. Add linked formulas for funding, operations, debt repayment, and investment returns, then check calculations and formatting while reviewing each major section with the user.
中文简介正在准备中。当前显示英语简介。
Inspect recent merges for leftover debug code, TODO comments, lint warnings, and technical debt, meaning deferred maintenance work. Create a prioritized cleanup list that separates small fix candidates from issues requiring human judgment.
中文简介正在准备中。当前显示英语简介。