technical debt tracker recipe

[Better-Boy]

Fixes #4709

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 6

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)
✅ Recipe 2: APPROVED (LOW risk)
✅ Recipe 3: APPROVED (LOW risk)
✅ Recipe 4: APPROVED (LOW risk)
✅ Recipe 5: APPROVED (LOW risk)
✅ Recipe 6: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[Copilot]

Pull Request Overview

This PR adds a comprehensive technical debt tracking system consisting of a main recipe and five sub-recipes. The system enables automated analysis of code repositories to identify and prioritize various forms of technical debt.

• Introduces a main technical-debt-tracker.yaml recipe that orchestrates five specialized analysis sub-recipes
• Creates five sub-recipes for analyzing complexity, test coverage, documentation, dependencies, and code duplication
• Provides parameterized configuration with sensible defaults for complexity thresholds, test coverage requirements, and dependency age limits

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
technical-debt-tracker.yaml	Main orchestrating recipe that coordinates five sub-recipes to produce a consolidated technical debt report with prioritized recommendations
complexity-analysis.yaml	Sub-recipe analyzing cyclomatic complexity, function length, nesting depth, and class size to identify overly complex code
test-coverage-analysis.yaml	Sub-recipe identifying untested code paths and suggesting missing test cases for critical functionality
documentation-analysis.yaml	Sub-recipe checking for missing or inadequate documentation in README, API docs, and inline comments
dependency-analysis.yaml	Sub-recipe auditing dependencies for outdated versions, security vulnerabilities, and maintenance issues
duplication-detection.yaml	Sub-recipe finding duplicated code blocks and suggesting refactoring strategies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The sub-recipe paths use ./sub-recipes/ but the actual directory is named subrecipes (without hyphen) as shown in the file structure. This will cause recipe lookup failures at runtime. Update all paths to use ./subrecipes/ instead.

Suggested change

	path: "./sub-recipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./sub-recipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./sub-recipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./sub-recipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./sub-recipes/duplication-detection.yaml"
	path: "./subrecipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./subrecipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./subrecipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./subrecipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./subrecipes/duplication-detection.yaml"

[Copilot]

The sub-recipe paths use ./sub-recipes/ but the actual directory is named subrecipes (without hyphen) as shown in the file structure. This will cause recipe lookup failures at runtime. Update all paths to use ./subrecipes/ instead.

Suggested change

	path: "./sub-recipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./sub-recipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./sub-recipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./sub-recipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./sub-recipes/duplication-detection.yaml"
	path: "./subrecipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./subrecipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./subrecipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./subrecipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./subrecipes/duplication-detection.yaml"

[Copilot]

The sub-recipe paths use ./sub-recipes/ but the actual directory is named subrecipes (without hyphen) as shown in the file structure. This will cause recipe lookup failures at runtime. Update all paths to use ./subrecipes/ instead.

Suggested change

	path: "./sub-recipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./sub-recipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./sub-recipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./sub-recipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./sub-recipes/duplication-detection.yaml"
	path: "./subrecipes/complexity-analysis.yaml"
	values:
	complexity_threshold: "{{ complexity_threshold }}"
	- name: "test_coverage_analyzer"
	path: "./subrecipes/test-coverage-analysis.yaml"
	values:
	min_coverage: "{{ min_test_coverage }}"
	- name: "documentation_analyzer"
	path: "./subrecipes/documentation-analysis.yaml"
	values:
	check_readme: "true"
	check_api_docs: "true"
	- name: "dependency_analyzer"
	path: "./subrecipes/dependency-analysis.yaml"
	values:
	max_age_days: "{{ max_dependency_age_days }}"
	check_vulnerabilities: "true"
	- name: "duplication_detector"
	path: "./subrecipes/duplication-detection.yaml"

[taniandjerry]

Tagging teammates to help review since it otherwise looks good! @blackgirlbytes @EbonyLouis

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 6

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)
✅ Recipe 2: APPROVED (LOW risk)
✅ Recipe 3: APPROVED (LOW risk)
✅ Recipe 4: APPROVED (LOW risk)
✅ Recipe 5: APPROVED (LOW risk)
✅ Recipe 6: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 6

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)
✅ Recipe 2: APPROVED (LOW risk)
✅ Recipe 3: APPROVED (LOW risk)
✅ Recipe 4: APPROVED (LOW risk)
✅ Recipe 5: APPROVED (LOW risk)
✅ Recipe 6: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[taniandjerry]

Thank you for addressing the feedback! This looks good, thank you so much for contributing ❤️