@mpstaton what platform did you use to make your plugins? I’ve never been able to get AI to do anything useful for me so would love to know.
Hey, was curious if you ever figured this out. I am in a very similiar spot at the moment. I’ve tried as many differerent things to re-summon the review bot as possible. I feel like I must just be missing a very obvious thing.
What PR?
1 Like
PR-8888
I’m nearly positive this is something I’m doing wrong, but I can’t for the life of me figure out what it is. Please let me know if there’s anything I can do, appreciate any help! 
The underlying issue should be fixed now, you just got a new review
I see it now, thank you! Appreciate the help!
If you had the code scan skipped via the /skip command, is there a way to have it scanned again?
I was arguing with the bot that my plugin was using proper sentence case. Eventually I just decided to skip the scan, as that was its only gripe, but ultimately decided to cave to make the bot happy to get green lights to hopefully not have the plugin lost in a backlog of “changes requested” “additional review required”.
If it’s helpful - my pull request:
I want to express my sincere gratitude for all the hard work you’ve been putting in 
.
With the developer guidelines an LLM one-shotted my plugin (almost). Which is HUGE. The plugin template is excellent and prevents the-blank-list problem. Code entities are carefully documented, which helps a lot. The integration with Svelte and TypeScript has significantly reduced many problems. Thanks for setting up the GitHub action; it’s almost perfect. The PR bot can be a bit noisy, but that’s just the way things work.
As a plugin developer, the only concern I have is the release cycle time. If there are any issues in production, I won’t be able to fix them quickly due to the moderation process. However, on the positive side, this means I have more time to further improve the plugin’s quality.
It would be great if the bot could provide an estimated time to completion based on the statistics of closed and approved PRs, as well as the time spent on each PR. I’ve noticed that the timing from opening a PR to approval is currently around 2-3 months.
In case anyone finds this - I released a new version to GitHub, which seemed to re-engage the auto-validation bot.
Last year I submitted two Obsidian plugins for review. The second, GitHub Tasks, went fairly smoothly. I think it took a couple of months from submission to release. Partly this is because I learned from the first, but it is also a very simple plugin.
The first, Co-Intelligence AI (PR #6690), was submitted June 10, and is still in limbo. The last actions were:
- ObsidianReviewBot finds no issues with the code, marks it for manual review (October 24)
- joethei assigned ObsidianReviewBot and unassigned joethei on Dec 3, 2025
- joethei removed the Changes made label on Dec 3, 2025
No further communication, no indication that I’m supposed to do anything, no indication of what to expect.
Before, this, on Oct 17, joethai apparently tried to merge the plugin, which presumably means it was accepted, but there was a mismatch between the plugin’s description in the PR and the repo. I fixed that immediately, and since then I’ve been waiting.
To be clear, I don’t begrudge that Obsidian has a small team or that plugin review is a slow process. I’m just frustrated at the lack of communication and transparency.
If you could code up an automation (@ObsidianTeam) to say in our PRs just how backlogged you are, then that would add some clarity to the uncertainty.