Show branch graph

I need the visual history right now — show the branch graph for this repo so I can see merges and where feature work diverged. Run the history with dates and short commit messages, laid out in a graph I can scan in my terminal, starting from HEAD back to three months.

Before I send this graph to the team, make the important branches obvious — highlight active branches and recent merges, show author initials and the date next to each tip, and collapse long linear stretches so reviewers can spot branches that need cleanup.

I just ran the history and the commit graph is a dense tangle; I need to know whether the branch named feature/login is the current working branch or if HEAD moved to main after a merge. I cannot tell from this output who merged what and when and I'm worried I might base further work on the wrong tip. What is the fastest, safest way to identify the active branch tips and recent merge points so I can proceed without breaking anyone's CI?

Across projects we let old topic branches pile up and the commit graph becomes unreadable; triage takes twice as long. I want a rule to keep the graph clear and make reviews faster. Which recurring habits should we adopt for branch naming, merge timing, and cleanup so active lines of work stay visible and stale branches get removed without disrupting anyone?