docs: add integration patterns guide and benchmark scope documentation#451
Open
kevglynn wants to merge 1 commit into
Open
docs: add integration patterns guide and benchmark scope documentation#451kevglynn wants to merge 1 commit into
kevglynn wants to merge 1 commit into
Conversation
Integration guide covers on-demand profile, anti-patterns (double injection, ultra as routine council member, standalone review as QA gate), and multi-agent review integration pattern. Benchmark scope doc clarifies task-type dependency, model-specific cost behavior, and independent evaluation findings. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
Two new documentation files based on findings from an independent evaluation:
Motivation
Ponytail's README covers installation for 16+ hosts but not integration patterns for projects with existing review systems or test frameworks. The benchmark results are honest about limitations (issue #126 response, agentic limitations), but scope and model-specific behavior deserve dedicated documentation.
Key content
Integration patterns:
Benchmark scope:
Test plan
npm testpasses (1 pre-existing failure in csv correctness test, unrelated to docs)Made with Cursor