Conversation
…eviewer command was helpful in suggestions for consistent styling. /cht-doc was helpful in quick guidance and questions. Something to build on.
…for its decision on whether to use MCP
|
@Hareet, I started reviewing this PR but haven't finished yet. I am mostly operating from a "do no harm" perspective and double-check for eventual inconsistencies. Question: Do we plan to also create |
| - [ ] Links validated | ||
| - [ ] Appropriate shortcodes used | ||
|
|
||
| Ask the user to confirm they want to proceed at each major step if the task is complex. |
There was a problem hiding this comment.
question: how would claude classify a task as complex?
There was a problem hiding this comment.
That's a good question.. for now, we can let it try to infer that. We should think about some examples or guard-rails. The current result of that should only mean more stops on easy tasks, which at least isn't negative.
Claude Skills can be used everywhere now, so users can point their setup to the Skill files. I was going to leave this as: people can port it or open a new PR for their preferred agent. It's a [ . ] folder, thinking along the lines of "if someone wanted to add a different cloud tool or gitlab-ci-runners" they could always add their [ . ] folder and not all similar ones. This is more of just a starting point. If people are using it and have questions about how to use it with other agents, we can support that at that time. |
|
Thanks for the review, @sugat009, and apologies for not finishing my review of this PR myself, either. One review is sufficient - let's merge it! |

Summary
Running /docs-review in Claude Code:
Recording.2026-01-14.211931.mp4