greyscript-linter

Analyze GreyScript code for errors before GreyHack builds.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Toqsick/MaxClaw --skill greyscript-linter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: greyscript-linter
Source: https://github.com/Toqsick/MaxClaw/tree/main/skills/greyscript-linter
Command: npx skills add https://github.com/Toqsick/MaxClaw --skill greyscript-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and prevent common errors in GreyScript code before the build process, ensuring cleaner builds and reducing debugging time.

Core Features & Use Cases

  • Static Analysis: Detects missing command markers, disallowed built-ins, and other common issues in GreyScript code.
  • Pre-Commit Hook: Integrates as a pre-commit hook for Git repositories to catch issues before code is committed.
  • Pre-Build Trigger: Triggers analysis before each greybel build to ensure code quality before compilation.

Quick Start

Run the lint-greyscript.py script on your GreyScript source file to check for common errors.

Frequently Asked Questions about greyscript-linter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch common GreyScript errors before running a build?

You can catch common GreyScript errors by performing static analysis on your source files before compilation. This detects missing command markers and disallowed built-ins early, ensuring cleaner builds and reducing debugging time.

Can I use a linter as a Git pre-commit hook for GreyHack development?

Yes, you can integrate static analysis as a Git pre-commit hook for GreyHack repositories. This automatically checks GreyScript code for common issues before changes are committed, preventing errors from entering version control.

What common GreyScript issues does static analysis detect?

Static analysis detects missing command markers, disallowed built-ins, and other common issues in GreyScript code. Identifying these problems before compilation helps maintain code quality and prevents build failures during GreyHack development.

Do I need Python to run static analysis on GreyScript code?

Yes, Python is required to run the static analysis script on GreyScript code. The linter relies on Python to process your source files and identify potential issues before the GreyHack build process begins.

How do I trigger code quality checks before a greybel build?

You can trigger code quality checks before each greybel build by integrating the linter into your build automation scripts. This pre-build analysis ensures your GreyScript code is evaluated for common errors before compilation occurs.