docs: retire the STYLE-CHECK convention - #831
Merged
Merged
Conversation
Stop enforcing the STYLE-CHECK marker in CodeRabbit and remove the marker that was rendering as visible text on the hosted-auth Next.js cookbook. Per reviewer request on PR #818: STYLE-CHECK markers should not be committed going forward. ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>
ekline
Bot
requested review from
AkshayParihar33,
amitash1912,
ravibits and
saif-at-scalekit
as code owners
July 3, 2026 07:15
saif-at-scalekit
enabled auto-merge (squash)
July 3, 2026 07:21
saif-at-scalekit
approved these changes
Jul 3, 2026
✅ Deploy Preview for scalekit-starlight ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
A reviewer on #818 asked that the
STYLE-CHECKmarker no longer be committed to the repo, that existing occurrences be removed, and that CodeRabbit stop enforcing it. This PR handles the repo-level part of that request.Changes
.coderabbit.yaml— removed the rule under theCLAUDE.mdpath instructions that required every AI-generated draft to end withSTYLE-CHECK: [PASSED | TODO]. CodeRabbit will no longer enforce the marker on future PRs.src/content/docs/cookbooks/add-hosted-auth-nextjs-app-router.mdx— removed a bareSTYLE-CHECK: PASSEDline that was committed at the end of the page. Because it was not wrapped in an MDX comment, it rendered as visible text on the published page.Related PRs
The same marker was introduced on three in-flight docs PRs; each has a follow-up commit removing it:
authenticate/mcp/troubleshooting.mdxagentkit/authentication/troubleshooting.mdxreference/find-identifiers-and-settings.mdxVerification
STYLE-CHECKoccurrences remain insrc/,.coderabbit.yaml,CLAUDE.md, orAGENTS.mdon this branch.developer-docs/CLAUDE.mdandAGENTS.mdwere checked and do not mentionSTYLE-CHECK(the "Quality Checklist" section never referenced it), so no edit was needed there.Out of scope
The monorepo-root
CLAUDE.md(outside this git repository) still contains aSTYLE-CHECKconvention line. It cannot be changed from adeveloper-docsPR — flagging it so whoever owns that file can update it separately.Preview:
https://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/cookbooks/add-hosted-auth-nextjs-app-router/ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>