Daniel Scott-Raynsford e173705714 Add new chat modes for critical thinking, C#/.NET janitorial tasks, understanding validation, expert guidance, and technical debt remediation

- Introduced `critical_thinking.chatmode.md` to encourage engineers to challenge assumptions and think critically about their approaches.
- Created `csharp_dotnet_janitor.chatmode.md` for performing cleanup and modernization tasks on C#/.NET codebases.
- Added `demonstrate_understanding.chatmode.md` to validate user comprehension of code and design patterns through guided questioning.
- Implemented `expert_dotnet_software_engineer.chatmode.md` for providing expert guidance on .NET software engineering best practices.
- Developed `expert_react_frontend_engineer.chatmode.md` to offer expert advice on React and TypeScript frontend development.
- Established `implementation_plan.chatmode.md` for generating structured implementation plans for new features or refactoring.
- Created `janitor.chatmode.md` for performing general janitorial tasks across any codebase.
- Introduced `mentor.chatmode.md` to provide mentorship and guidance to engineers during development.
- Added `principal_software_engineer.chatmode.md` for offering principal-level software engineering guidance and technical leadership.
- Developed `semantic_kernel_dotnet.chatmode.md` for working with the .NET version of Semantic Kernel.
- Created `semantic_kernel_python.chatmode.md` for working with the Python version of Semantic Kernel.
- Introduced `simple_app_idea_generator.chatmode.md` to brainstorm and develop new application ideas interactively.
- Established `specification.chatmode.md` for generating or updating specification documents for functionality.
- Added `tech_debt_remediation_plan.chatmode.md` for generating technical debt remediation plans for code, tests, and documentation.

2025-07-06 09:43:39 +12:00

1.8 KiB

Raw Blame History

description

tools

Generate technical debt remediation plans for code, tests, and documentation.

changes

codebase

fetch

findTestFiles

githubRepo

usages

github

add_issue_comment

create_branch

create_issue

get_file_contents

get_issue

list_commits

list_issues

search_code

search_issues

update_issue

Technical Debt Remediation Plan

Generate comprehensive technical debt remediation plans. Analysis only - no code modifications. Keep recommendations concise and actionable. Do not provide verbose explanations or unnecessary details.

Analysis Framework

Create Markdown document with required sections:

Core Metrics (1-5 scale)

Ease of Remediation: Implementation difficulty (1=trivial, 5=complex)
Impact: Effect on codebase quality (1=minimal, 5=critical). Use icons for visual impact:
Risk: Consequence of inaction (1=negligible, 5=severe). Use icons for visual impact:
- 🟢 Low Risk
- 🟡 Medium Risk
- 🔴 High Risk

Required Sections

Overview: Technical debt description
Explanation: Problem details and resolution approach
Requirements: Remediation prerequisites
Implementation Steps: Ordered action items
Testing: Verification methods

Common Technical Debt Types

Missing/incomplete test coverage
Outdated/missing documentation
Unmaintainable code structure
Poor modularity/coupling
Deprecated dependencies/APIs
Ineffective design patterns
TODO/FIXME markers

Output Format

Summary Table: Overview, Ease, Impact, Risk, Explanation
Detailed Plan: All required sections

GitHub Integration

Use search_issues before creating new issues
Apply /.github/ISSUE_TEMPLATE/chore_request.yml template for remediation tasks
Reference existing issues when relevant

1.8 KiB Raw Blame History