Jonverrier

4 ms·

1. 1.▲
   by Jonverrier 5mo ago

   Some technical commentary. There is a consumer guide that sets out how to use the package. In essence you decide which controls you want, if they are warnings or prevention, and then we generate a guardrails.yaml which is used by the GitHub
2. 2.▲
   Show HN: RipStop – Git guardrails to reduce impact if your code agent goes wild(github.com)

   2 points by Jonverrier 5mo ago|1 comments
3. 3.▲
   C4-Auto – CLI that auto-generates C4 architecture docs for TypeScript(github.com)

   1 points by Jonverrier 7mo ago|1 comments
4. 4.▲
   by Jonverrier 7mo ago

   A few months ago I shared C4-Agent, an MCP server that generates C4-style docs and Mermaid diagrams from your codebase while you work in the IDE. It’s flexible and interactive, but depends on MCP, and the Agents, even now, seem to drift off
5. 5.▲
   Show HN: Requirement Linter, an AI-powered tool to improve software requirements(github.com)

   1 points by Jonverrier 1y ago|0 comments
6. 6.▲
   Show HN: Standardising 'Unit Tests' for Prompts(github.com)

   3 points by Jonverrier 2y ago|0 comments
7. 7.▲
   by Jonverrier 2y ago

   Hi, I had a look at Bela.live. Thanks for the link, it’s obviously very comprehensive. Philosophically, I don’t think these tools should be storing things in their own database - I think the diagrams / markup should be going back to th
8. 8.▲
   Show HN: AI-Powered Documentation Generator for Legacy Codebases(github.com)

   8 points by Jonverrier 2y ago|2 comments