AI Prompts for Identify Type Safety Violations

Please provide the exact output from the last build that indicates a TypeScript type violation related to [SPECIFIC FILE OR MODULE]. Include the line number where the violation occurred and detail the incorrect type assertion that was made. Format your response to clearly highlight the line number, the type assertion, and any relevant context around the violation.

Please provide the full error message from the build tab related to TypeScript type safety issues. I want to analyze this error to determine the root cause of the problem. Ensure that you include any relevant context or code snippets that may help in understanding the issue better.

Please summarize your understanding of the instruction regarding TypeScript type safety. Include key points such as the importance of strict mode, common pitfalls that may arise, and how to ensure compliance with type safety standards. Your summary should be clear and concise, ideally structured in bullet points for easy reference.

Identify the expected type behavior for the function located in [FILE] at line [LINE]. Then, compare this expected behavior with the actual implementation. Highlight any discrepancies between the two, providing specific examples of how the actual implementation deviates from the expected type behavior. Present your findings in a clear and structured format, outlining each discrepancy and its implications.

Analyze the last output and identify the specific TypeScript rule or constraint that was violated. Provide the exact clause from the TypeScript documentation that applies to this violation, and explain how it relates to the output. Format your response by first stating the violated rule, followed by the quoted clause, and then a brief explanation of the violation.

Please identify the variable at [FILE]:[LINE] that is currently typed as 'any' in the TypeScript code. Change its type to [SPECIFIC TYPE] to enforce stricter type checking. After making the change, provide me with a diff of the code that shows the modification before applying it.

Identify the incorrect type assertion in the code located at [FILE] on line [LINE]. The original assertion was: [PASTE]. The modified assertion is: [PASTE]. Please revert the assertion back to its original form and provide the diff output that highlights the changes made.

Please remove the ts-ignore comment located at [FILE]:[LINE] in the code. After removing the comment, ensure that the code complies with TypeScript's strict mode by checking for any type errors or warnings. Provide a summary of the changes made and confirm that the code is now compliant.

Identify the function located at [FILE] on line [LINE] that does not conform to the expected type format. Rewrite this function to align with the following structure: [EXPECTED FORMAT]. Please provide a comparison of the original and revised code, highlighting the changes made.

Verify the imports in [FILE] for compliance with TypeScript's strict mode. Ensure that all imported types are correctly defined and utilized in the code. If you find any incorrect imports, please correct them and provide a detailed explanation of the changes made, including the original and updated code snippets for clarity.

Please run a build test for the TypeScript project after applying the necessary fixes. Confirm that the output is free of TypeScript errors and provide a detailed report of the results, including any warnings or issues encountered during the build process. Format the report to include sections for the test summary, error details if any, and overall conclusions.

Please provide the diff of the changes made to [FILE]. Ensure that you highlight any modifications related to type safety issues and confirm that they have been addressed correctly. Present the output in a clear format, indicating the lines added, removed, or modified, along with any relevant comments explaining the changes.

Replay the original scenario that resulted in the TypeScript error in your code. Provide a detailed description of the steps you took to reproduce the error, including any relevant code snippets. After confirming that the scenario now runs without any type-related issues, summarize the changes made to resolve the error and explain why they were effective.

Please test the following edge case that previously caused a type safety violation in TypeScript: [EDGE CASE DESCRIPTION]. Confirm whether it now behaves as expected without any errors. Provide a detailed explanation of the test results, including any changes made to the code and how they resolved the issue.

Please check the output of the file [FILE] after implementing the necessary fixes. Confirm that the output matches the expected type outputs and ensure that there are no errors present. Provide a summary of your findings, including any discrepancies or issues that may arise.

Please create a session-opening constraint for a TypeScript project that enforces type safety. The constraint should state: 'Before any code execution, verify that all types are explicitly defined and that no 'any' types are used. If any violations are detected, stop the execution and alert the developer before proceeding. Ensure that no deployment occurs without full compliance with type safety standards.' Format this as a clear and concise guideline for developers to follow.

Please create a conversation-starter template for reviewing type assertions in TypeScript. The template should include a checklist with the following points: confirm that the type is explicitly defined, ensure it matches the expected structure, and if there are discrepancies, provide a suggestion for correction. Format the output as a bullet-point list that can be easily referenced during code reviews.

Please add a code comment guard in [FILE] that states: '/* Ensure all variables are typed explicitly. Do not use 'any' or ts-ignore comments. */'. This comment should be placed at the top of the file to serve as a reminder for future code changes. Additionally, explain the importance of strict typing in TypeScript and how it can prevent potential bugs in the codebase.

Create a project convention message for our team regarding TypeScript type safety. The message should clearly state that 'All team members must adhere to strict TypeScript type definitions. Any code submitted must pass type checks before merging.' Additionally, explain the importance of maintaining type safety and how it contributes to the overall quality of our codebase. Format this as a formal announcement that can be shared with the team.

Please create a self-check request for type safety in TypeScript files. Before deploying, ensure that all TypeScript files are free of 'any' types and 'ts-ignore' comments. If any instances of these are found, provide a detailed report and halt the deployment process until the issues are resolved.