name	cleanup
description	Comprehensive code cleanup and quality assurance for .NET solutions. Compiles, formats, lints, removes dead code, and synchronizes documentation with code. Use this skill whenever you are asked to cleanup the solution, repository, branch, project, etc.

Cleanup Skill

Path Convention: All paths in this file are relative to this file's location (.github/skills/cleanup/).
Therefore, ../../../ refers to the workspace root (/workspaces/techhub/).

Code Cleanup Skill

Maintain code quality, consistency, and documentation accuracy for Tech Hub.

🎯 Core Workflow

Each step:

Run script (link provided)
Read template if exists (link provided)
Present findings in chat (don't write to file unless specifically useful)
Wait for user input (template guides options)

Scripts output raw data. YOU analyze and format using templates.

Cleanup Steps

Execute in order. Don't skip or proceed if a step fails.

Step 1: Build & Test

Run: Run -Clean with IsBackground: false to verify a clean build and test pass.

Requirements: 0 errors, all tests pass.

If tests fail: Read docs/running-and-testing.md to understand proper test execution, debugging workflows, and using Run parameters. Fix all issues and retry before Step 2.

Step 2: Code Formatting

Run: format-code.ps1

Applies dotnet format per .editorconfig rules.

Step 2a: CSS Token Analysis

Script 1: Count-TokenUsage.ps1
Script 2: Find-UndefinedTokens.ps1
Template: css-token-analysis-template.md

Script 1 counts usage of each CSS color token defined in design-tokens.css
Script 2 finds CSS color references that don't exist in design-tokens.css
Analyze the data to identify:
- Unused tokens (candidates for removal)
- Single-use tokens (consolidation opportunities)
- Undefined references (bugs - must fix)
Present summary in chat with your recommendations using template
Wait for user input

Color Token Categories:

Multi-use (2+): Core design tokens, keep these
Single-use (1): Review if they should be consolidated with existing tokens
Unused (0): Safe to remove unless reserved for future use
Undefined: BUGS - references that must be fixed or removed

Step 3: Code Quality Analysis

Script: analyze-code-quality.ps1
Template: overview-template.md

Script outputs warnings/errors by priority (High/Medium/Low)
Analyze the data and provide smart recommendations
Present summary in chat with your recommendations using template
Wait for user input

Step 4: Fix or Suppress

Apply Step 3 decisions. If there was nothing to improve immediately go to step 5.

Step 5: Dead Code Detection

Script: find-dead-code.ps1
Template: dead-code-report-template.md

Script finds unused members, commented code, unused CSS
Analyze findings, identify false positives
Present summary in chat with your recommendations using template
Wait for user approval

Tech Hub Architecture Patterns (script auto-filters these):

Minimal API Endpoint Handlers (src/TechHub.Api/Endpoints/*.cs):
- Methods registered via MapGet(), MapPost(), etc. appear "unused"
- Static analysis can't detect delegate method group references
- Script behavior: Automatically skips these files
Blazor Event Handlers (*.razor.cs):
- Methods bound via @onclick, @onchange, etc. appear "unused"
- Static analysis can't detect Blazor event binding expressions
- Script behavior: Automatically skips these files
Unused Parameters (common in these scenarios):
- Minimal API handlers: Injected dependencies for future use
- Middleware constructors: Standard ASP.NET Core parameters (next, logger, environment)
- ContentFixer utility: Placeholder parameters for planned features
- Script behavior: Automatically skips Endpoints/, Middleware, ContentFixer files
Build Artifacts:
- Compiler-generated code in bin/, obj/, .tmp/ directories
- Script behavior: Excluded via Get-SourceFiles helper function

If you see false positives, these patterns explain why. Verify the file location matches one of the above before reporting as dead code.

Roslyn Analyzer Configuration:

The project uses built-in .NET analyzers for build-time dead code detection configured in .editorconfig:

IDE0051: Unused private member detection
IDE0052: Unread private member detection
IDE0060: Remove unused parameter
File-Specific Suppressions: src/TechHub.Api/Endpoints/*.cs suppresses unused parameter warnings (intentional injected dependencies)

Analysis Settings: Configured in Directory.Build.props:

AnalysisLevel: latest-all
AnalysisMode: All
Documentation generation enabled for comprehensive IntelliSense

Step 5a: Project Analysis

No script - YOU analyze.
Template: project-analysis-template.md

Analyze implementation (endpoints, components, services, models)
Analyze documentation (API spec, AGENTS.md, functional docs)
Analyze tests (unit, integration, component, E2E)
Identify gaps (undocumented, untested, stale)
Present summary in chat with your recommendations using template
Wait for user decision

Step 6: Documentation Review

Step 6a: Run Documentation Quality Checks

Run: verify-documentation.ps1

This performs quality checks:

Expected Files: Verifies presence of key documentation files
Broken Links: Detects broken internal markdown links
Missing AGENTS.md: Checks if code directories lack AGENTS.md files

Step 6b: Analyze Documentation

No script - YOU analyze using verification results.

Use the verification results to:

Verify all features are documented (compare with Step 5a)
Check documentation is in the right location
Identify duplicate or overlapping documentation
Fix any broken links found by verify script
Ensure missing AGENTS.md files are created if needed
Ensure cross-references are complete

Present summary in chat with your recommendations.

Step 7: Test Review

No script - YOU analyze.
Template: test-review-template.md
Read: tests/AGENTS.md

Scan tests for violations (AAA, naming, positioning, coverage)
Analyze quality and assign grade (A-F)
Present summary in chat with your recommendations using template
Wait for user approval

Step 8: Best Practices

No script - YOU use grep_search.
Template: best-practices-template.md

grep_search for anti-patterns
Read files to verify context
Analyze findings and categorize by severity
Present summary in chat with your recommendations using template
Wait for user approval

Search: .Count(?!\(\)), .Result|.Wait\(\), async void, catch.*\{\s*\}

Step 9: Final Validation

Run to verify nothing broke: Execute Run -Clean

Checklist:

0 errors
Reduced warnings
All tests pass
No new diagnostics

Report success or issues.

Rules

Don't Remove:

// Intentional: comments
Documented .editorconfig suppressions
Test helpers (xUnit discovery)
Blazor parameters
Minimal API handlers

Ask First: Public APIs, debug code, component parameters

name	cleanup
description	Comprehensive code cleanup and quality assurance for .NET solutions. Compiles, formats, lints, removes dead code, and synchronizes documentation with code. Use this skill whenever you are asked to cleanup the solution, repository, branch, project, etc.

Cleanup Skill

Path Convention: All paths in this file are relative to this file's location (.github/skills/cleanup/).
Therefore, ../../../ refers to the workspace root (/workspaces/techhub/).

Code Cleanup Skill

Maintain code quality, consistency, and documentation accuracy for Tech Hub.

🎯 Core Workflow

Each step:

Run script (link provided)
Read template if exists (link provided)
Present findings in chat (don't write to file unless specifically useful)
Wait for user input (template guides options)

Scripts output raw data. YOU analyze and format using templates.

Cleanup Steps

Execute in order. Don't skip or proceed if a step fails.

Step 1: Build & Test

Run: Run -Clean with IsBackground: false to verify a clean build and test pass.

Requirements: 0 errors, all tests pass.

If tests fail: Read docs/running-and-testing.md to understand proper test execution, debugging workflows, and using Run parameters. Fix all issues and retry before Step 2.

Step 2: Code Formatting

Run: format-code.ps1

Applies dotnet format per .editorconfig rules.

Step 2a: CSS Token Analysis

Script 1: Count-TokenUsage.ps1
Script 2: Find-UndefinedTokens.ps1
Template: css-token-analysis-template.md

Script 1 counts usage of each CSS color token defined in design-tokens.css
Script 2 finds CSS color references that don't exist in design-tokens.css
Analyze the data to identify:
- Unused tokens (candidates for removal)
- Single-use tokens (consolidation opportunities)
- Undefined references (bugs - must fix)
Present summary in chat with your recommendations using template
Wait for user input

Color Token Categories:

Multi-use (2+): Core design tokens, keep these
Single-use (1): Review if they should be consolidated with existing tokens
Unused (0): Safe to remove unless reserved for future use
Undefined: BUGS - references that must be fixed or removed

Step 3: Code Quality Analysis

Script: analyze-code-quality.ps1
Template: overview-template.md

Script outputs warnings/errors by priority (High/Medium/Low)
Analyze the data and provide smart recommendations
Present summary in chat with your recommendations using template
Wait for user input

Step 4: Fix or Suppress

Apply Step 3 decisions. If there was nothing to improve immediately go to step 5.

Step 5: Dead Code Detection

Script: find-dead-code.ps1
Template: dead-code-report-template.md

Script finds unused members, commented code, unused CSS
Analyze findings, identify false positives
Present summary in chat with your recommendations using template
Wait for user approval

Tech Hub Architecture Patterns (script auto-filters these):

Minimal API Endpoint Handlers (src/TechHub.Api/Endpoints/*.cs):
- Methods registered via MapGet(), MapPost(), etc. appear "unused"
- Static analysis can't detect delegate method group references
- Script behavior: Automatically skips these files
Blazor Event Handlers (*.razor.cs):
- Methods bound via @onclick, @onchange, etc. appear "unused"
- Static analysis can't detect Blazor event binding expressions
- Script behavior: Automatically skips these files
Unused Parameters (common in these scenarios):
- Minimal API handlers: Injected dependencies for future use
- Middleware constructors: Standard ASP.NET Core parameters (next, logger, environment)
- ContentFixer utility: Placeholder parameters for planned features
- Script behavior: Automatically skips Endpoints/, Middleware, ContentFixer files
Build Artifacts:
- Compiler-generated code in bin/, obj/, .tmp/ directories
- Script behavior: Excluded via Get-SourceFiles helper function

If you see false positives, these patterns explain why. Verify the file location matches one of the above before reporting as dead code.

Roslyn Analyzer Configuration:

The project uses built-in .NET analyzers for build-time dead code detection configured in .editorconfig:

IDE0051: Unused private member detection
IDE0052: Unread private member detection
IDE0060: Remove unused parameter
File-Specific Suppressions: src/TechHub.Api/Endpoints/*.cs suppresses unused parameter warnings (intentional injected dependencies)

Analysis Settings: Configured in Directory.Build.props:

AnalysisLevel: latest-all
AnalysisMode: All
Documentation generation enabled for comprehensive IntelliSense

Step 5a: Project Analysis

No script - YOU analyze.
Template: project-analysis-template.md

Analyze implementation (endpoints, components, services, models)
Analyze documentation (API spec, AGENTS.md, functional docs)
Analyze tests (unit, integration, component, E2E)
Identify gaps (undocumented, untested, stale)
Present summary in chat with your recommendations using template
Wait for user decision

Step 6: Documentation Review

Step 6a: Run Documentation Quality Checks

Run: verify-documentation.ps1

This performs quality checks:

Expected Files: Verifies presence of key documentation files
Broken Links: Detects broken internal markdown links
Missing AGENTS.md: Checks if code directories lack AGENTS.md files

Step 6b: Analyze Documentation

No script - YOU analyze using verification results.

Use the verification results to:

Verify all features are documented (compare with Step 5a)
Check documentation is in the right location
Identify duplicate or overlapping documentation
Fix any broken links found by verify script
Ensure missing AGENTS.md files are created if needed
Ensure cross-references are complete

Present summary in chat with your recommendations.

Step 7: Test Review

No script - YOU analyze.
Template: test-review-template.md
Read: tests/AGENTS.md

Scan tests for violations (AAA, naming, positioning, coverage)
Analyze quality and assign grade (A-F)
Present summary in chat with your recommendations using template
Wait for user approval

Step 8: Best Practices

No script - YOU use grep_search.
Template: best-practices-template.md

grep_search for anti-patterns
Read files to verify context
Analyze findings and categorize by severity
Present summary in chat with your recommendations using template
Wait for user approval

Search: .Count(?!\(\)), .Result|.Wait\(\), async void, catch.*\{\s*\}

Step 9: Final Validation

Run to verify nothing broke: Execute Run -Clean

Checklist:

0 errors
Reduced warnings
All tests pass
No new diagnostics

Report success or issues.

Rules

Don't Remove:

// Intentional: comments
Documented .editorconfig suppressions
Test helpers (xUnit discovery)
Blazor parameters
Minimal API handlers

Ask First: Public APIs, debug code, component parameters

cleanup

Cleanup Skill

Code Cleanup Skill

🎯 Core Workflow

Cleanup Steps

Step 1: Build & Test

Step 2: Code Formatting

Step 2a: CSS Token Analysis

Step 3: Code Quality Analysis

Step 4: Fix or Suppress

Step 5: Dead Code Detection

Step 5a: Project Analysis

Step 6: Documentation Review

Step 6a: Run Documentation Quality Checks

Step 6b: Analyze Documentation

Step 7: Test Review

Step 8: Best Practices

Step 9: Final Validation

Rules

Mehr aus diesem Repository

Cleanup Skill

Code Cleanup Skill

🎯 Core Workflow

Cleanup Steps

Step 1: Build & Test

Step 2: Code Formatting

Step 2a: CSS Token Analysis

Step 3: Code Quality Analysis

Step 4: Fix or Suppress

Step 5: Dead Code Detection

Step 5a: Project Analysis

Step 6: Documentation Review

Step 6a: Run Documentation Quality Checks

Step 6b: Analyze Documentation

Step 7: Test Review

Step 8: Best Practices

Step 9: Final Validation

Rules

Mehr aus diesem Repository