I claim this task.

it's yours!

DoNotUseReservedInEnumValueNamesRule

It is considered bad practice to define reserved values in enums. This rule 
warns if
any value contains the word reserved.

Bad example:

enum Answer {
    Yes,
    No,
    Maybe,
    Reserved
}

Good example:

enum Answer {
    Yes,
    No,
    Maybe
}



DoNotPrefixValuesWithEnumNameRule

This rule checks for enum values that are prefixed with the enum's name.

Bad example:

enum Answer {
    AnswerYes,
    AnswerNo,
    AnswerMaybe,
}

Good example:

enum Answer {
    Yes,
    No,
    Maybe
}


ParameterNamesShouldMatchOverridenMethodRule

This rule warns if an overriden method's parameter names do not match those of 
the
base class (or those of the implemented interface).

Bad example:

class Base {
    public abstract void Write (string text);
}

class SubType : Base {
    public overwrite void Write (string output)
    {
        //...
    }
}
Good example:

class SubType : Base {
    public overwrite void Write (string text)
    {
        //...
    }
}

The new zip format, compressing 9kb down to 0kb. Sadly it's not working...

0kb seems like the holy grail - too bad it didn't work out ;-)

DoNotPrefixValuesWithEnumNameRule
* Nice trick on field.IsStatic to check for value__ (and like all nice hacks 
it's
worth a comment ;-)
* RuleSuccess == null, so you can return a null MessageCollection (the rules 
with
null checks are because we cannot return an empty MessageCollection, but it 
doesn't
apply here since you don't create one until you need it :-)
* I'm not sure about the FalsePositive case, where the enum value == enum 
name... it
seems bad naming to me. Could you add another test case while I think about it 
(and
ask around) ?
* Just to get 100% coverage (always nice even if it doesn't mean perfection) 
add a
test case for a non-enum. E.g. using the test fixture class itself is ok.

DoNotUseReservedInEnumValueNamesRule
* same comments (except for false positive ;-)

got to go now... will review ParameterNamesShouldMatchOverridenMethodRule later 
(or
tomorrow). Thanks!

> public overwrite void Write (string output)

Didn't know there are _overwritten_ methods in C# =P

ParameterNamesShouldMatchOverridenMethodRule looks ok, expect for the extra line
TypeDefinition type = (TypeDefinition) method.DeclaringType;
which is unneeded (at least in the attached version).

I won't have time to test it until tonight but, as I don't expect any problem, 
so you
can go ahead and claim another task.

* Nice trick on field.IsStatic to check for value__ (and like all nice hacks 
it's
worth a comment ;-)
Thanks :)
* RuleSuccess == null, so you can return a null MessageCollection (the rules 
with
null checks are because we cannot return an empty MessageCollection, but it 
doesn't
apply here since you don't create one until you need it :-)
Removed it.
* I'm not sure about the FalsePositive case, where the enum value == enum 
name... it
seems bad naming to me. Could you add another test case while I think about it 
(and
ask around) ?
I have added a test case + code that also warns if enum value == enum name (old 
code
is commented out)
* Just to get 100% coverage (always nice even if it doesn't mean perfection) 
add a
test case for a non-enum. E.g. using the test fixture class itself is ok.
Done

Changed overwrite to override in ParameterNamesShouldMatchOverridenMethodRule's
warning message.

It's all in SVN. Thanks!

p.s. "and like all nice hacks it's worth a comment ;-)" I meant a source code 
comment ;-)