JSONschema support for custom DevSkim rules

Is your feature request related to a problem? Please describe.
Yes, the documentation is really lacking and I'm having a very hard time getting things to work. A JSONSchema for custom rules would not only help validate the formatting it would be the ultimate documentation and test (that could be embedded even) and really help feedback for custom rule development.

Describe the solution you'd like
A complete JSONSchema description for the Custom Rule format for DevSkim.

Describe alternatives you've considered
XST.

Additional context

Here is a start, very incomplete but I still wouldn't know how to use all advanced features of DevSkim (such as ymlpath):

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Generated schema for Root",
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "name": {
        "type": "string"
      },
      "id": {
        "type": "string"
      },
      "description": {
        "type": "string"
      },
      "recommendation": {
        "type": "string"
      },
      "applies_to": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "confidence": {
        "type": "string"
      },
      "severity": {
        "type": "string"
      },
      "rule_info": {
        "type": "string"
      },
      "patterns": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "pattern": {
              "type": "string"
            },
            "type": {
              "type": "string"
            },
            "scopes": {
              "type": "array",
              "items": {
                "type": "string"
              }
            }
          },
          "required": [
            "pattern",
            "type",
            "scopes"
          ]
        }
      },
      "fix_its": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "name": {
              "type": "string"
            },
            "type": {
              "type": "string"
            },
            "replacement": {
              "type": "string"
            },
            "pattern": {
              "type": "object",
              "properties": {
                "pattern": {
                  "type": "string"
                },
                "type": {
                  "type": "string"
                },
                "scopes": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                }
              },
              "required": [
                "pattern",
                "type",
                "scopes"
              ]
            }
          },
          "required": [
            "name",
            "type",
            "replacement",
            "pattern"
          ]
        }
      },
      "must-match": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "must-not-match": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "required": [
      "name",
      "id",
      "description",
      "recommendation",
      "applies_to",
      "tags",
      "confidence",
      "severity",
      "rule_info",
      "patterns",
      "fix_its",
      "must-match",
      "must-not-match"
    ]
  }
}

Also helpful:

• https://transform.tools/json-to-json-schema
• https://www.jsonschemavalidator.net/
• https://json-schema.org/

Start by locating DevSkim's custom rule format and existing rule definitions, then compare their fields and advanced features with the proposed schema. The work is done when the schema covers the complete custom-rule format, including features such as ymlpath, and can validate representative custom rules.