<commit_before><!--
Remove any section(s) that does not apply to this pull request.
-->

### Submitting new cogs

So, you want to submit a new cog for DecoraterBot? Awesome. Now first things first, does it meet these requirements?

Does your submition:

- [ ] Have every line of code at 79 characters or less.
- [ ] Is not error prone (does not raise exceptions)
- [ ] If it experiences an Error, does it catch it and try to retry using another method (if possible) or does it allert the bot owner or server owner that the bot cannot send messages in a server / channel (if configured).
- [ ] Meets PEP8 on hangling line indents.
- [ ] Does not have hacks to avoid issues.
- [ ] Follow examples of the current existing cogs on how they are made with an append to ``self.bot.commands_list`` to update the list when your cog is loaded and is removed from the list when unloaded.

### Patching or editing cogs

So, you patched a bug or optimized a cog or command? Good work. How do you meet these requirements?

Does your edit:

- [ ] Have every line of code at 79 characters or less.
- [ ] Is not error prone (does not raise exceptions)
- [ ] If it experiences an Error, does it catch it and try to retry using another method (if possible) or does it allert the bot owner or server owner that the bot cannot send messages in a server / channel (if configured).
- [ ] Meets PEP8 on hangling line indents.
<commit_msg>Update PULL_REQUEST_TEMPLATE.md<commit_after><!--
Remove any section(s) that does not apply to this pull request.
-->

### Submitting new cogs

So, you want to submit a new cog for DecoraterBot? Awesome. Now first things first, does it meet these requirements?

Does your submition:

- [ ] Have every line of code at 79 characters or less.
- [ ] Is not error prone (does not raise exceptions)
- [ ] If it experiences an Error, does it catch it and try to retry using another method (if possible) or does it allert the bot owner or server owner that the bot cannot send messages in a server / channel (if configured).
- [ ] Meets PEP8 on hangling line indents.
- [ ] Does not have hacks to avoid issues.
- [ ] Follow examples of the current existing cogs on how they are made with an all commands fed into ``self.bot.add_commands`` as a list to update the list when your cog is loaded and is removed from the list with ``self.bot.remove_commands`` with the same list when unloaded.

### Patching or editing cogs

So, you patched a bug or optimized a cog or command? Good work. How do you meet these requirements?

Does your edit:

- [ ] Have every line of code at 79 characters or less.
- [ ] Is not error prone (does not raise exceptions)
- [ ] If it experiences an Error, does it catch it and try to retry using another method (if possible) or does it allert the bot owner or server owner that the bot cannot send messages in a server / channel (if configured).
- [ ] Meets PEP8 on hangling line indents.

{'fraction_non_alphanumeric': 0.06404109589041096, 'fraction_numerical': 0.00410958904109589, 'mean_word_length': 3.6661341853035143, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5808875', 'n_tokens_mistral': 796, 'n_tokens_neox': 777, 'n_words': 482}