Like some others have noted, I'm conflicted about PC for the same reason that I have been conflicted by versions of Lint for C and C++. That being the need to more easily reduce the 'error/warning' checks to something useful. I often feel that any code that makes it through with no output is either written by the gods or is too trivial to consider. Somewhat like Godel's notions about un-decidability.
That said a PC module I'd certainly like to see would be based on 'Effective Perl Programming'. Strictly based, nothing else need apply. It also occurs to me that it would be nice to have named modules that could be the basis of a given run. This would of course allow the addition of local needs and caveats. Perhaps all of this is available now, it has been a while since I've looked(for the disclaimed reasons above) In any even EPP should be on every Perl programmers desk(alright bookshelf for you neat-freaks) as it is the best introduction to idiomatic Perl of any text out there. Yes it says that on the cover, but that doesn't prevent it from being correct.
in reply to Where are the Perl::Critic policies for the Camel?
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."