Thank you for your contributions! 🙌 After reviewing the provided snippets, here’s the feedback:

1. Please read our Contributing Guidelines carefully, some snippets doesn't follow our guidelines because the usage section is either missing the title or improperly formatted. Here the right example:

def example_function_call()
 ...
end
# Usage:
example_function_call()

some snippet have # Usage without colon or # Example Usage, consistency will help to make QuickSnip a better repo.

2. The following snippets do not align with the scope of QuickSnip and should be removed:

• singly-linked-list
• doubly-linked-list
• binary-tree

QuickSnip focuses on self-contained functions that solve specific problems or perform distinct tasks. Full classes, like the ones provided, are outside the scope of what we accept. These implementations are fundamental data structures that are widely available in tutorials and documentation, which doesn’t add significant value as standalone snippets.

3. Changes for truncate-string:

   • The parameter order (max_length, str) is unconventional. Typically, the string being operated on is the first parameter, followed by additional options. Please change it to str, max_length for better readability and consistency.
   • Add a guard clause to handle cases where max_length is less than 3, as this would result in a negative index for str[0, max_length - 3].

4. Improvements for camel-case-to-snake-case:

   • You could add support for PascalCase easily. Currently, the implementation leaves a leading underscore if the string starts with an uppercase letter.
   • Suggested fix:

     str.gsub(/([A-Z])/, '_1円').sub(/^_/, '').downcase

If you have any questions or need clarification, feel free to leave a comment on your PR.

Little naming issue, but appart from that it looks good

Great work