How do you incorporate PSScriptAnalyzer as part of your dev process?

My team wants to leverage this utility to ensure consistent coding practices for all of our custom commandlets. I was hoping to have a discussion and get some insight into how other teams and developers use PSScriptAnalyzer as part of their dev process.

Some questions to get this going:

• What triggers your analysis? Is it manually run by developers as needed? Does it run as part of your postbuild process? Only in certain build configurations? If it does run with each build, does the build fail if Warnings or Errors are generated?
• Are the results only for the developer running the analysis to review in their console, or do you take the results and do something with them?
• How have you addressed performance issues / slowdowns caused by analysis of many Powershell scripts at once?

I realize all teams and organizations are different, and one team's process isn't necessarily going to work for everyone, but I am interested in recommendations for what processes you find work well for yourself and your team.

The issue does not name any files, tests, or entry points. It asks for process recommendations around PSScriptAnalyzer, including triggers, build behavior, result handling, and performance. There is no concrete completion criterion for a first-time contributor.