Community Feedback
If you try RepoDocs AI on a real API or documentation workflow, the most useful feedback is concrete and specific.
Where To Respond
- Open a GitHub Discussion
- Open an issue if you hit a repeatable failure
What Feedback Helps Most
Share answers to these questions:
- What was clear within the first few minutes?
- What was confusing, slow, or too detailed?
- Did the payments example make the output feel credible?
- If you tried your own OpenAPI spec, where did the workflow help and where did it break?
- What would make you comfortable adopting this in a real repository?