Yes.
- Describe the development environment using docker-compose. The motivation, initially, was not wanting to have development libraries installed natively in my PC; now it's not having to install everything manually in every developer's computer, as well as having a centralized and easily editable development environment.
- Run tests on pre-commit hook. The motivation was to force me to write more tests (as well as more easily testable code), to prevent leaking errors.
- CI-tool integrated with VCS server that runs tests in an environment similar to production after every push. The motivation was, again, preventing errors.
- Deploy to staging server on successful automatic tests, with the same CI-Tool. The motivation was not having to mind deployment to staging every time.
I've also written simple shell scripts for other, minor, things.
EDIT: This guide I wrote covers how to get started on everything from the list.