I'm a Senior Software Engineer who was called out on the following:1. Having too many PRs open, closed, and in draft
2. Having too many commits
3. Too many comments from others in my PRs
4. Pushing commented code & code with git artifacts in itIn my defense:1. Since Q1, my team has reprioritized a lot of work. There hasn't been a discussion about what to do with the work that we all started. Also, I open a draft PR the moment I make my first commit on a branch, for visibility.2. I commit a lot. Commits are my safety net. I use `git reset` tremendously throughout the day to go back to different states in the code I'm working on.3. The director expects senior engineers to have very little chatter on their PRs. They should be ready to merge with little discussion. What he didn't see was that most of the comments are from Hound, our linter. Rather than linting before pushing, I enjoy waiting for Hound's comments and fixing them afterward.4. I made a mistake. I've been forced to comment out code recently in some of our microservices as a temporary fix while working locally. I forgot to uncomment the code before pushing to GitHub. The director went through my commits and saw some commit messages like "uncomment code", "remove commented block", and reprimanded me for that.I've been an engineer for 10+ years and no one has called me out on any of this. This is how I like to work. I don't see a real problem here.I can squash my commits, lint locally, and stay blocked when services aren't working on my machine. But I'm mostly concerned about why this director is calling out this bullsh*t.I spoke to my former manager, and he said it'd just be easier to appease him. But it feels like the director is looking for a reason to let me go by finding incompetencies in my performance. I do not want to work in fear or with paranoia.Should I have a chat with the director's manager to ask about the feedback and what he suggests I do about it?