Getting clients, managers, project managers, designers, and developers on the same page when it comes to feature expectations is hard. Everyone speaking the same language (literally) can go a long way to achieving the same, metaphorically.
There are three common formats that are great for written and verbal communication between stakeholders with different backgrounds, responsibilities, and risk exposures. They are each natural-language, narrative formats (they use plain english) that anyone can understand, but their structrued nature is proven to help clearly communicate behavior, specify intent and synchronize expectations.
save this as `.git/hooks/post-merge` in any of your repos. Then, when you do a `git pull` (or really any merge I think), if any migrations were updated or the Gemfile was edited, you'll get a handy reminder to migrate or bundle install.