docs: add mastra-axi to community catalog - #101
Open
taltas wants to merge 1 commit into
Open
Conversation
4 tasks
taltas
force-pushed
the
feat/mastra-axi-catalog
branch
2 times, most recently
from
July 22, 2026 00:19
d5841fd to
5136b23
Compare
taltas
force-pushed
the
feat/mastra-axi-catalog
branch
from
July 22, 2026 18:48
5136b23 to
58d2967
Compare
This was referenced Jul 24, 2026
Open
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
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.
Intent
Add mastra-axi to the AXI community catalog as a documentation-only contribution. Append exactly one catalog.yaml community entry using the requested name, repository URL, author, Mastra domain, and one-sentence description copied from mastra-axi's README; preserve the existing field order and style. Regenerate README.md and docs/index.html from catalog.yaml rather than editing generated regions by hand, do not touch release-please-generated files, validate formatting, lint, and docs synchronization, then push to the taltas/axi fork and open a PR against kunchenguid/axi main through no-mistakes without merging it.
What Changed
Risk Assessment
✅ Low: Documentation-only change adding a single catalog entry with properly regenerated files, all validation checks pass, and the change exactly follows the established catalog pattern.
Testing
Validated the mastra-axi catalog entry through automated checks (docs:check, format:check, lint) and manual diff analysis. All validation checks passed, confirming the catalog entry was properly added with correct structure, generated files were synchronized from catalog.yaml, and no release-please files were touched.
Evidence: Validation Summary
All user intent requirements satisfied: ✅ Single catalog.yaml entry added with all required fields ✅ Field order and style preserved ✅ README.md and docs/index.html regenerated (not hand-edited) ✅ Release-please files untouched ✅ Formatting validated (Prettier passes) ✅ Linting validated (ESLint passes) ✅ Docs synchronization validated (docs:check passes)Evidence: Catalog Context
mastra-axi entry appended at end of community catalog with all required fields in correct orderEvidence: docs:check output
Evidence: format:check output
Evidence: lint output
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
✅ **Review** - passed
✅ No issues found.
✅ **Test** - passed
✅ No issues found.
pnpm run docs:check- verified generated files synchronizationpnpm run format:check- verified Prettier formattingpnpm run lint- verified ESLint compliancegit diffanalysis - verified catalog.yaml entry structure and field ordergit diffanalysis - verified README.md and docs/index.html were regenerated correctlygit diff --name-only- verified no release-please files were modified✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.