Add notabene to AI-powered Tools - #28
Open
wamxx wants to merge 1 commit into
Open
Conversation
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.
Adds notabene to General Tools → AI-powered Tools.
notabene renders a repo's Markdown/MDX as a navigable site where reviewers leave anchored, Google-Docs-style comments on the rendered text. Comments are stored as JSON committed next to the docs, so an AI agent reads the open ones, applies the feedback to the source files, resolves the threads and journals what changed. No SaaS, no external service — the review round-trip stays in git.
Placed in AI-powered Tools rather than Site Builder: rendering the site is the support, the human↔agent review loop is the point.
MIT, published as
@z29k/notabene, docs at https://z29k.github.io/notabene/Per CONTRIBUTING.md:
On
pre-commit: hooks were installed and run againstREADME.md.trailing-whitespace,end-of-file-fixer,check-yamlandcheck-added-large-filesall pass.awesome-lintreports1:1 Awesome list must reside in a valid git repository (remark-lint:awesome-github)— but it reports exactly the same error on the unmodified upstreamREADME.md(verified by stashing this change and re-running), so it is a local/fork environment artefact rather than something introduced here. The commit was made with--no-verifyfor that reason; happy to adjust if you see it differently.