chore: update ci (#2574)

Author: olimorris

.github/pull_request_template.md

@@ -16,7 +16,6 @@
 ## Checklist
 
 - [ ] I've read the [contributing](https://github.com/olimorris/codecompanion.nvim/blob/main/CONTRIBUTING.md) guidelines and have adhered to them in this PR
-- [ ] I've added [test](https://github.com/olimorris/codecompanion.nvim/blob/main/CONTRIBUTING.md#testing) coverage for this fix/feature
-- [ ] I've run `make all` to ensure docs are generated, tests pass and my formatting is applied
-- [ ] _(optional)_ I've updated `CodeCompanion.has` in the [init.lua](https://github.com/olimorris/codecompanion.nvim/blob/main/lua/codecompanion/init.lua#L239) file for my new feature
+- [ ] I've run `make all` to ensure docs are generated, tests pass and [StyLua](https://github.com/JohnnyMorganz/StyLua) has formatted my code
+- [ ] _(optional)_ I've added [test](https://github.com/olimorris/codecompanion.nvim/blob/main/CONTRIBUTING.md#testing) coverage for this fix/feature
 - [ ] _(optional)_ I've updated the README and/or relevant docs pages

.github/workflows/require-checklist.yml

@@ -0,0 +1,18 @@
+name: Require Checklist
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize]
+  issues:
+    types: [opened, edited, deleted]
+
+jobs:
+  check-tasks:
+    runs-on: ubuntu-latest
+    if: github.event.pull_request.user.login != 'dependabot[bot]' and github.event.pull_request.user.login != 'olimorris' and github.event.pull_request.draft == false
+    steps:
+      - uses: mheap/require-checklist-action@v2
+        with:
+          requireChecklist: false
+          skipDescriptionRegex: .*\(optional\).*
+          skipDescriptionRegexFlags: i

CONTRIBUTING.md

@@ -27,20 +27,13 @@ They're located [here](https://codecompanion.olimorris.dev) and are regularly up
 
 ### Use Rules
 
-When working inside the CodeCompanion repository, you have access to the built-in [rule](https://codecompanion.olimorris.dev/usage/chat-buffer/rules) files. These give an LLM knowledge of how a certain aspect of the plugin has been implemented. If you're looking to add a new feature to CodeCompanion, memory is a great way of ensuring you follow existing practices and that your LLM fully understands the architecture and design decisions that have been made.
+When working inside the CodeCompanion repository, you have access to the built-in [rule](https://codecompanion.olimorris.dev/usage/chat-buffer/rules) files. These give an LLM knowledge of how a certain aspect of the plugin has been implemented. If you're looking to add a new feature to CodeCompanion, rules are a great way of ensuring you follow existing practices and that your LLM fully understands the architecture and design decisions that have been made.
 
-You can load memory into the chat via the Action Palette:
+You can load rules into the chat via the Action Palette:
 
 <img src="https://github.com/user-attachments/assets/7ea80fd0-136e-4d7e-9d70-f4d08dec005c">
 
-Or, via the `/rules` slash command. Currently, the memory files that have been added are:
-
-- ACP
-- Adapters
-- Chat
-- Tests
-- Tools
-- UI
+Or, via the `/rules` slash command.
 
 ### Refer to the Tests