All skills
ailabs-393 avatar

/tech-debt-analyzer

@7d5342d

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

Use this Skill: https://skilld.dev/gh/ailabs-393/ai-labs-claude-skills/tech-debt-analyzer

This session only. Nothing lands on disk.

assetsADR_TEMPLATE.md

≈605 tokens on demand. Your agent reads this file only when SKILL.md points to it.

ADR-XXX: [Short Title of Decision]

Status: [Proposed / Accepted / Deprecated / Superseded]

Date: [YYYY-MM-DD]

Deciders: [List of people involved in the decision]

Technical Story: [Description, ticket/issue URL]


Context and Problem Statement

[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.]

Key Constraints:

  • [List any constraints that limit the solution space]

Key Requirements:

  • [List must-have requirements]

Decision Drivers

[List the factors that influenced the decision, e.g.:]

  • [driver 1, e.g., performance requirement]
  • [driver 2, e.g., team expertise]
  • [driver 3, e.g., cost constraints]
  • [etc.]

Considered Options

Option 1: [Name]

Description: [Brief description of this option]

Pros:

  • [good, because...]
  • [good, because...]

Cons:

  • [bad, because...]
  • [bad, because...]

Effort: [Estimated effort]


Option 2: [Name]

Description: [Brief description of this option]

Pros:

  • [good, because...]
  • [good, because...]

Cons:

  • [bad, because...]
  • [bad, because...]

Effort: [Estimated effort]


Option 3: [Name]

[Repeat structure for each option considered]


Decision Outcome

Chosen option: "[Option X: Name]"

Rationale: [Explain why this option was chosen. What makes it the best choice given the context and decision drivers?]


Consequences

Positive Consequences

  • [e.g., improvement of quality attribute satisfaction, follow-up decisions required, ...]
  • [...]

Negative Consequences

  • [e.g., compromising quality attribute, follow-up decisions required, ...]
  • [...]

Technical Debt

[Any technical debt being incurred as a result of this decision? How will it be tracked?]


Implementation

Action Items:

  • [Implementation task 1]
  • [Implementation task 2]
  • [etc.]

Timeline: [Expected implementation timeline]

Rollback Plan: [How to revert this decision if needed]


Validation

Success Metrics: [How will we measure if this decision was correct?]

Review Date: [When should we review this decision?]


References

  • [Link to supporting documents]
  • [Link to related ADRs]
  • [Link to research/benchmarks]

Notes

[Any additional notes, context, or discussion points]

Source: SKILL.md on GitHub

No alerts13d5 checks · Risk SAFE
  • Gen Agent Trust Hub13d

    This skill provides automated tools for identifying technical debt in JavaScript and TypeScript projects. It performs local static analysis on source code and dependency files to generate reports on code quality and project health. No malicious behavior or security vulnerabilities were identified.

  • Socket13d

    No alerts

  • Snyk13d

    Risk: LOW · No issues

  • Runlayer7mo

    2/8 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 7d5342d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 11 months ago

README badge

README badge for ailabs-393/ai-labs-claude-skills/tech-debt-analyzer