Example 1:
Instruction: Remove the dragon_string variable and print the result directly to simplify the code logic.
Action: "Remove the dragon_string variable" refers to the removal of some intermediate within the code. Therefore, we have category: "remove-intermediate-variable"

Example 2:
Instruction: Define a function to handle range updates, simplify conditional judgments, and reduce redundant code.
Action: "Define a function" refers to abstracting logic into a seperate function. Therefore, we have category: "encapsulate-code-into-a-function"

Example 3:
Instruction: avoid coding outside the function 
Action: "coding outside the function" implies that code exists in a global context that is not a part of a function which should be fixed. Therefore, we have category: "encapsulate-code-into-a-function"

Example 4:
Instruction: Avoid using long if-else chains based on loops.
Action: "avoid using long if-else chains" refers to long chains of if-else blocks which should be refactored. Therefore, we have category: "shorten-if-else-chains"

Example 5:
Instruction: Use the built-in max() function to reduce the if statements.
Action: "Use the built-in max() function" refers to instructions that suggest or require refactoring existing code patterns using the max or min function. Therefore, we have category: "use-max/min"

Example 6:
Instruction: Avoid declaring module names that are meaningless.
Action: "module names that are meaningless" refers to variable/class names that are not named with descriptive names. Therefore, we have category: "more-descriptive-variable-names"

Example 7:
Instruction: Replace abbreviations with more descriptive variable names.
Action: "more descriptive variable names" refers to instructions that require updated and more descriptive variable names. Therefore, we have category: "more-descriptive-variable-names"