mirror of
https://github.com/mattermost/mattermost.git
synced 2026-08-26 21:27:40 -05:00
Eva SarafianouandCursor
7c3fad1475
Six reader personas review changes under docs/main, docs/develop and docs/api, and one sticky comment per PR carries their verdicts. Advisory only: nothing blocks a merge, and the review is a no-op when ANTHROPIC_API_KEY is unset, so forks and unconfigured checkouts are unaffected. The registry is the set of files in .github/prompts/personas/, each carrying its metadata in frontmatter, so adding a persona means adding a file. Rules that don't vary by audience live in conventions.md and review-contract.md instead of being restated six times, and they form a byte-identical prefix across personas so they hit the prompt cache. Conventions were derived by measuring docs/ rather than ported from the migration PoC, which corrected three wrong assumptions: title is the only required frontmatter key, plan gating is <PlanAvailability slug>, and internal links are absolute site paths. No prose linter runs. The Vale config already in the repo comes from the PoC and has never been run against this corpus; it produces ~8,375 findings, most of them false positives, so brand-voice judges heading case and terminology in context instead. This change leaves those files untouched and records the measurement in the docs-ai README, so whether they should stay at all can be decided separately. Co-authored-by: Cursor <cursoragent@cursor.com>
15 lines
330 B
JSON
15 lines
330 B
JSON
{
|
|
"name": "mattermost-docs-ai",
|
|
"version": "1.0.0",
|
|
"private": true,
|
|
"type": "module",
|
|
"description": "AI review pipeline for docs/ — persona registry, router, persona review, report.",
|
|
"scripts": {
|
|
"test": "node --test"
|
|
},
|
|
"dependencies": {
|
|
"@anthropic-ai/sdk": "^0.40.0",
|
|
"js-yaml": "^4.1.0"
|
|
}
|
|
}
|