User story.
As a custom rule developer I'd like to implement rules in such a way that check are performed if there is a marker field is absent in document, and skipped otherwise

Is your feature request related to a problem?
I have special schemas that are not subject to say info-contact check and they are marked by info:skip-contact: true field.

the core rule is quite simple

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

Project References help us to build specic package.

Currently, we need to build before developing a specifc package.

cd <project-root>
yarn run build

We need to enforce \n for line breaks.

A really simple task. The best first issue. We have a huge lack of tests. Write tests for anything inside, be creative 🔥

Most js projects have configured linters in package.json as npm run script to pass on arguments to eslint and start it for example with npm run lint:eslint.

Suggestion: make it possible to run a linter unsing this npm run configuration, otherwise you have to maintain paraleters for all linters in two locations: package.json and github action file.