Add more rule documentations

Author: yutingc

RuleDocumentation/MissingModuleManifestField.md

@@ -0,0 +1,14 @@
+#MissingModuleManifestField 
+**Severity Level: Warning**
+
+
+##Description
+
+Some fields of the module manifest (such as ModuleVersion) are required.
+
+##How to Fix
+
+Please consider adding the missing fields to the manifest.
+
+##Example
+

RuleDocumentation/PossibleIncorrectComparisonWithNull.md

@@ -0,0 +1,30 @@
+#PossibleIncorrectComparisonWithNull 
+**Severity Level: Warning**
+
+
+##Description
+
+Checks that $null is on the left side of any equaltiy comparisons (eq, ne, ceq, cne, ieq, ine). When there is an array on the left side of a null equality comparison, PowerShell will check for a $null IN the array rather than if the array is null. If the two sides of the comaprision are switched this is fixed. Therefore, $null should always be on the left side of equality comparisons just in case.
+
+##How to Fix
+
+Please consider moving null on the left side of the comparison.
+##Example
+
+Wrong： 
+
+	function CompareWithNull
+	{
+	    if ($DebugPreference -eq $null) 
+	    {
+	    }
+	}
+
+Correct: 
+
+	function CompareWithNull
+	{
+	    if ($null -eq $DebugPreference) 
+	    {
+	    }
+	}

RuleDocumentation/ProvideCommentHelp.md

@@ -0,0 +1,71 @@
+#ProvideCommentHelp 
+**Severity Level: Info**
+
+
+##Description
+
+Checks that all cmdlets have a help comment. This rule only checks existence. It does not check the content of the comment.
+
+
+##How to Fix
+
+Please consider adding help comment for each cmdlet.
+
+##Example
+
+Wrong:
+
+    function Verb-Files
+    {
+        [CmdletBinding(DefaultParameterSetName='Parameter Set 1', 
+                      SupportsShouldProcess=$true, 
+                      PositionalBinding=$false,
+                      HelpUri = 'http://www.microsoft.com/',
+                      ConfirmImpact='Medium')]
+        [Alias()]
+        [OutputType([String])]
+        Param
+        (
+            ...
+        )
+       
+    }
+
+Right:
+
+    <#
+    .Synopsis
+       Short description
+    .DESCRIPTION
+       Long description
+    .EXAMPLE
+       Example of how to use this cmdlet
+    .EXAMPLE
+       Another example of how to use this cmdlet
+    .INPUTS
+       Inputs to this cmdlet (if any)
+    .OUTPUTS
+       Output from this cmdlet (if any)
+    .NOTES
+       General notes
+    .COMPONENT
+       The component this cmdlet belongs to
+    .ROLE
+       The role this cmdlet belongs to
+    .FUNCTIONALITY
+       The functionality that best describes this cmdlet
+    #>
+    function Get-File
+    {
+        [CmdletBinding(DefaultParameterSetName='Parameter Set 1', 
+                      SupportsShouldProcess=$true, 
+                      PositionalBinding=$false,
+                      HelpUri = 'http://www.microsoft.com/',
+                      ConfirmImpact='Medium')]
+        [Alias()]
+        [OutputType([String])]
+        Param
+        (
+            ...
+        )
+    }

RuleDocumentation/ProvideVerboseMessage.md

@@ -0,0 +1,14 @@
+#ProvideVerboseMessage 
+**Severity Level: Warning**
+
+
+##Description
+
+Checks that Write-Verbose is called at least once in every cmdlet or script. This is in line with the PowerShell best practices.
+
+##How to Fix
+
+Please consider adding Write-Verbose in each cmdlet.
+
+##Example
+

RuleDocumentation/UseApprovedVerbs.md

@@ -0,0 +1,28 @@
+#UseApprovedVerbs 
+**Severity Level: Warning**
+
+
+##Description
+
+All defined cmdlets must use approved verbs. This is in line with PowerShell's best practices.
+
+##How to Fix
+
+Please consider using full cmdlet name instead of alias. 
+
+##Example
+
+Wrong： 
+
+    function Change-Item
+    {
+        ...
+    }
+
+Correct: 
+    
+    function Update-Item
+    {
+        ...
+    }
+

RuleDocumentation/UseCmdletCorrectly.md

@@ -0,0 +1,22 @@
+#UseCmdletCorrectly 
+**Severity Level: Error**
+
+
+##Description
+
+Cmdlets must be invoked with the correct syntax and parameters. For example, calling Set-Date with no parameters would be triggered by this rule since it has a required date parameter. 
+
+##How to Fix
+
+To fix a violation of this rule, please use mandatory parameters when calling cmdlets.
+
+##Example
+
+Wrong： 
+
+	set-date
+
+Correct: 
+
+	$t = get-date
+	set-date -date $t