Debugging Runtime Errors with GitHub Copilot

Prompt 1: Troubleshooting Common Runtime Errors

Intent: To help developers debug runtime errors using GitHub Copilot.

Prompt:
  Youare debugging a runtime error in your code. The error details are as follows #error_type: {error_type}
  error_type: "TypeError"
execution_environment: {execution_environment}

Analyze the error and provide:
- Explanation of the error
- Potential causes
- Code fixes with clear explanations
- Prevention tips

Prompt 2: Debugging Patterns with GitHub Copilot

Debugging Strategy Template

Intent: To guide systematic debugging using GitHub Copilot.

Prompt: You are debugging an issue in your code. Describe:
- Error symptoms
- Reproduction steps
- Environment details
- Recent changes

Example debugging flow:
error_type: "Runtime Exception"
symptoms: "Application crashes when processing large files"
environment: "Production server"
recent_changes: "Added parallel processing feature"

Debugging Best Practices

1. Systematic Approach
2. Gather all relevant information
3. Form and test hypotheses
4. Document findings

5. Verify fixes

6. Tool Integration

7. Use debugging tools effectively
8. Integrate logging systems
9. Monitor system metrics

10. Track error patterns

11. Prevention Strategies

12. Add validation checks
13. Implement monitoring
14. Use type safety
15. Handle edge cases

Anti-patterns to Avoid

1. Debugging Pitfalls
2. Console.log debugging in production
3. Incomplete error handling
4. Ignoring error patterns

5. Missing root cause analysis

6. Process Issues

7. No reproduction steps
8. Incomplete documentation
9. Untested fixes
10. Ignored warning signs