trustmebro.reviews
Git

Git

Software Tool · Developer & AI coding tools · 11 mentions · 2 subreddits · discussed in r/PromptEngineering, r/ISO27001

Reddit take

Not enough linked mention summaries yet; the source excerpts below are the evidence.

Pros

  • VScode, Git, Roo, Custom agents in Roo made specifically for creating agents and prompts. Works amazingly well.
  • absolutely a best practice and good grc engineering principles. I am doing the same. git blame, git log, using .md for policy and SOPs, proving version control through "reviews", my reviews are "commit hashes".
  • Use an IDE. Use Git. Done.
  • Forget Notion for version control—it’s fine for docs, but you need Git for real workflow.
  • Git works for any files, not just code.

Cons

  • To be fair, it's not user friendly to the engineers either.
  • For the engineering team it is perfect. For the rest of the organisation it’s not very user friendly
  • Git is great if you're focussing on technical detail, but may be less user-friendly to the people who operate or own the more difficult controls around people, process, policy¹, risk...?

Sentiment

8 positive (73%) · 2 mixed (18%) · 1 negative (9%)

Trust + time weighted score: +59% · raw score 64%

What redditors said (10 of 11)

VScode, Git, Roo, Custom agents in Roo made specifically for creating agents and prompts. Works amazingly well.
positive · u/m****g · r/PromptEngineering · comment · Dec 22, 2025 · open on Reddit ↗
To be fair, it's not user friendly to the engineers either.
negative · u/N****2 · r/ISO27001 · comment · Dec 19, 2025 · open on Reddit ↗
For the engineering team it is perfect. For the rest of the organisation it’s not very user friendly
mixed · u/f****o · r/ISO27001 · comment · Dec 18, 2025 · open on Reddit ↗
Git is great if you're focussing on technical detail, but may be less user-friendly to the people who operate or own the more difficult controls around people, process, policy¹, risk...?
mixed · u/U****t · r/ISO27001 · comment · Dec 18, 2025 · open on Reddit ↗
absolutely a best practice and good grc engineering principles. I am doing the same. git blame, git log, using .md for policy and SOPs, proving version control through "reviews", my reviews are "commit hashes".
positive · u/E****5 · r/ISO27001 · comment · Dec 18, 2025 · open on Reddit ↗
Use an IDE. Use Git. Done.
positive · u/m****g · r/PromptEngineering · comment · Dec 7, 2025 · open on Reddit ↗
Forget Notion for version control—it’s fine for docs, but you need Git for real workflow.
positive · u/T****9 · r/PromptEngineering · comment · Nov 27, 2025 · open on Reddit ↗
Git works for any files, not just code.
positive · u/U****s · r/PromptEngineering · comment · Nov 8, 2025 · open on Reddit ↗
One option is to install Git on all your computers, install Sourcetree, create a private repo on Github, put your prompts there, create a pdf with all your prompts in it, give that pdf to your llm with all those prompts in it, ask it to create a "prompt chooser" that when given some content describing your situation will choose the right prompt for your situation, and when you face problems do a writeup explaining the problem, feed it to the prompt chooser, and it will choose a prompt for you.
positive · u/z****f · r/PromptEngineering · comment · Jul 6, 2025 · open on Reddit ↗
By using Git and Obsidian together, and combining GitHub with Obsidian Sync, I think most needs are pretty well covered.
positive · u/K****i · r/PromptEngineering · comment · Jul 2, 2025 · open on Reddit ↗

Compare

Related