Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ast-grep-setup .claude/skills/ast-grep-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .claude/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ast-grep-setup .agents/skills/ast-grep-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .agents/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ast-grep-setup .cursor/skills/ast-grep-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .cursor/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alchemiststudiosDOTai/harness-engineering.git --path skills/ast-grep-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ast-grep-setup .gemini/skills/ast-grep-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .gemini/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ast-grep-setup .github/skills/ast-grep-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .github/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering ast-grep-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ast-grep-setup .opencode/skills/ast-grep-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ast-grep-setup" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/ast-grep-setup into .opencode/skills/ast-grep-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ast-grep-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ast-grep-setupSet up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs.
Ast Grep Setup is an agent skill from alchemiststudiosDOTai/harness-engineering. Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs. Creates sgconfig.yml, rule files, and rule tests. Use when adding structural linting, banning legacy patterns, or implementing ratchet gates.
Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts (for example `scripts/validate-rule.py`, `templates/rule-tests/no-console-log-test.yml` and `templates/rule-tests/no-debugger-test.yml`).
It sits in Development, covering Linting and formatting. It works with TypeScript. The repository describes itself as: harness-engineering discussion of shortcuts, automation, hacks and overall productivity with code agents like claude code, codex, and other harness. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7a9fa15. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3nodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ast Grep Setup loads about 4.7k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 581 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from alchemiststudiosDOTai/harness-engineering at commit 7a9fa15, republished under its MIT licence (© alchemiststudiosDOTai). 581 words, ~4,671 tokens.
.claude/skills/ast-grep-setup/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.Set up ast-grep with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs.
Agents: Before writing any rules, read the YAML Structure Rules section.
The most common mistakes are:
constraints inside rule: (must be at top level)not: blocksall: or any:Use the validation script to catch these before running ast-grep:
python3 scripts/validate-rule.py rules/*.yml# Create sgconfig.yml in project root
mkdir -p rules/ast-grep/rules rules/ast-grep/rule-tests
cat > rules/ast-grep/sgconfig.yml << 'EOF'
ruleDirs:
- rules
testConfigs:
- testDir: rule-tests
allowedFixers: []
EOFSee the Rule Library below for ready-to-use rules.
# Scan the codebase
cd rules/ast-grep && ast-grep scan
# Run rule tests
cd rules/ast-grep && ast-grep test
# Update test snapshots after rule changes
cd rules/ast-grep && ast-grep test -UPrevents function parameters without explicit types (implicit any).
# rules/no-implicit-any-params.yml
id: no-implicit-any-params
language: TypeScript
severity: warning
message: "Parameter '$PARAM' lacks explicit type annotation"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
pattern: function $FUNC($PARAM) { $$$BODY }
constraints:
PARAM:
not:
has:
kind: type_annotationBans direct property access on any typed values.
# rules/no-unsafe-any-usage.yml
id: no-unsafe-any-usage
language: TypeScript
severity: error
message: "Unsafe property access on 'any' type. Cast or add type guard."
rule:
pattern: $EXPR.$PROP
constraints:
EXPR:
typeAnnotation: anyPrevents unhandled promises that could fail silently.
# rules/no-floating-promises.yml
id: no-floating-promises
language: TypeScript
severity: error
message: "Promise is not awaited, returned, or handled with .catch()"
files:
- src/**/*.ts
- src/**/*.tsx
ignores:
- new Promise($$$)
- Promise.$FUNC($$$)
rule:
all:
- pattern: $PROMISE_FUNC($$$ARGS)
- has:
kind: call_expression
pattern: $PROMISE_FUNC($$$ARGS)
- not:
inside:
kind: await_expression
stopBy: end
- not:
inside:
kind: return_statement
stopBy: end
- not:
inside:
kind: call_expression
pattern: $$$.catch($$$)
stopBy: end
constraints:
PROMISE_FUNC:
regex: (fetch|axios\.[a-z]+|async|\.then)Detects async function calls without await.
# rules/no-missing-await.yml
id: no-missing-await
language: TypeScript
severity: warning
message: "Async function '$FUNC' called without await"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
all:
- pattern: $FUNC($$$ARGS)
- not:
inside:
kind: await_expression
stopBy: end
- not:
inside:
kind: return_statement
stopBy: end
constraints:
FUNC:
typeAnnotation: /^Promise</Bans empty catch blocks that swallow errors.
# rules/no-empty-catch.yml
id: no-empty-catch
language: TypeScript
severity: error
message: "Empty catch block silently swallows errors. Log or re-throw."
files:
- src/**/*.ts
- src/**/*.tsx
rule:
all:
- pattern: try { $$$TRY } catch ($ERROR) { $$$CATCH }
- not:
has:
kind: statement
inside:
kind: catch_clause
pattern: $$$CATCH
#### require-error-logging
Requires error logging in catch blocks.
```yaml
# rules/require-error-logging.yml
id: require-error-logging
language: TypeScript
severity: warning
message: "Catch block should log the error"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
all:
- pattern: try { $$$TRY } catch ($ERR) { $$$CATCH }
- not:
has:
kind: call_expression
pattern: console.$LOG($ERR)
inside:
kind: catch_clause
pattern: $$$CATCH
- not:
has:
kind: call_expression
pattern: logger.$LOG($ERR)
inside:
kind: catch_clause
pattern: $$$CATCHFlags useEffect hooks that might be missing dependencies.
# rules/no-use-effect-missing-deps.yml
id: no-use-effect-missing-deps
language: TypeScript
severity: warning
message: "useEffect has an empty dependency array but references external values"
files:
- src/**/*.tsx
rule:
pattern: useEffect($FUNC, [])
constraints:
FUNC:
has:
kind: identifier
pattern: $ID
not:
pattern: consolePrevents direct state mutation in React.
# rules/no-direct-state-mutation.yml
id: no-direct-state-mutation
language: TypeScript
severity: error
message: "Do not mutate state directly. Use the setter function."
files:
- src/**/*.tsx
rule:
all:
- pattern: $STATE.$PROP = $VAL
- has:
kind: identifier
pattern: $STATE
regex: ^set[A-Z]Warns about using reduce to build objects (often less readable).
# rules/no-array-reduce-for-objects.yml
id: no-array-reduce-for-objects
language: TypeScript
severity: warning
message: "Consider using Object.fromEntries() or a for...of loop instead of reduce for building objects"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
pattern: $ARR.reduce(($ACC, $ITEM) => { $$$BODY; return $ACC; }, {})Prevents regex creation inside loops (compiles on each iteration).
# rules/no-regex-in-loop.yml
id: no-regex-in-loop
language: TypeScript
severity: warning
message: "Creating regex inside loop - move outside or use constant"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
inside:
kind: for_statement
stopBy: end
pattern: /$PAT/Enforces module boundaries (customize for your architecture).
# rules/no-cross-module-imports.yml
id: no-cross-module-imports
language: TypeScript
severity: error
message: "Domain modules should not import from other domain modules directly"
files:
- src/domain/**/*.ts
rule:
all:
- pattern: import $$$ from "$MOD"
- matches:
source: $MOD
contains: /domain/Prevents Node.js modules from being imported in frontend code.
# rules/no-node-in-frontend.yml
id: no-node-in-frontend
language: TypeScript
severity: error
message: "Node.js built-in modules cannot be used in frontend code"
files:
- src/frontend/**/*.ts
- src/frontend/**/*.tsx
- src/client/**/*.ts
- src/client/**/*.tsx
rule:
all:
- pattern: import $$$ from "$MOD"
- matches:
source: $MOD
regex: ^(fs|path|os|crypto|http|https|net|dgram|dns|cluster|module|vm|child_process|worker_threads)$Prevents console.log in production code (use a logger instead).
# rules/no-console-log.yml
id: no-console-log
language: TypeScript
severity: warning
message: "Use a proper logger instead of console.log"
files:
- src/**/*.ts
- src/**/*.tsx
ignores:
- "**/*.test.ts"
- "**/*.spec.ts"
- "**/__tests__/**"
rule:
pattern: console.log($$$ARGS)Prevents debugger statements.
# rules/no-debugger.yml
id: no-debugger
language: TypeScript
severity: error
message: "Remove debugger statement before committing"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
pattern: debugger;Suggests const when variable is never reassigned.
# rules/prefer-const-over-let.yml
id: prefer-const-over-let
language: TypeScript
severity: hint
message: "Consider using 'const' since this variable is never reassigned"
files:
- src/**/*.ts
- src/**/*.tsx
rule:
all:
- pattern: let $VAR = $INIT
- not:
follows:
pattern: $VAR = $NEWVAL
stopBy: endEach rule should have a corresponding test file:
id: no-floating-promises
valid:
- |
const result = await fetch('/api/users');
- |
return fetch('/api/users');
- |
fetch('/api/users').catch(err => console.error(err));
- |
new Promise((resolve) => setTimeout(resolve, 1000));
- |
Promise.all([fetch('/a'), fetch('/b')]);
invalid:
- |
function getUsers() {
fetch('/api/users');
}
- |
async function load() {
fetch('/api/data');
}To implement a ratchet (block new violations while allowing existing ones):
# 1. Generate baseline of current violations
ast-grep scan --json > baseline/violations.json
# 2. Create baseline extractor script
cat > tools/ast-grep/baseline-check.sh << 'SCRIPT'
#!/bin/bash
# Check only new violations against baseline
ast-grep scan --json | node -e '
const baseline = require("./baseline/violations.json");
const current = JSON.parse(require("fs").readFileSync(0, "utf-8"));
const baselineSet = new Set(baseline.map(v => `${v.file}:${v.line}:${v.ruleId}`));
const newViolations = current.filter(v => !baselineSet.has(`${v.file}:${v.line}:${v.ruleId}`));
if (newViolations.length > 0) {
console.error("New violations found:");
newViolations.forEach(v => console.error(`${v.file}:${v.line} - ${v.message}`));
process.exit(1);
}
'
SCRIPT
chmod +x tools/ast-grep/baseline-check.sh# .github/workflows/ast-grep.yml
name: ast-grep
on: [push, pull_request]
jobs:
ast-grep:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node
uses: actions/setup-node@v4
- name: Install ast-grep
run: npm install -g @ast-grep/cli
- name: Run ast-grep scan
run: cd rules/ast-grep && ast-grep scan
- name: Run rule tests
run: cd rules/ast-grep && ast-grep testVS Code: Install the "ast-grep" extension for inline highlighting.
inside, follows, precedes for contextstopBy: end or stopBy: neighbor| Pattern | Matches |
|---|---|
function $FUNC($$$PARAMS) { $$$BODY } | Function declarations |
const $VAR = $EXPR | Const declarations |
$EXPR.$PROP | Property access |
import $$$ from "$MOD" | Import statements |
export $KIND $NAME | Export declarations |
$FUNC($$$ARGS) | Function calls |
await $EXPR | Await expressions |
try { $$$TRY } catch ($ERR) { $$$CATCH } | Try-catch |
$ARR.map($FN) | Array methods |
STOP: Read this before writing rules. These are the most common mistakes agents make.
constraints Goes at TOP LEVELWRONG - constraints inside rule:
id: bad-example
rule:
pattern: import $NAME from $MOD
constraints: # ❌ WRONG: constraints inside rule
MOD:
regex: "fs"RIGHT - constraints at top level:
id: good-example
rule:
pattern: import $NAME from $MOD
constraints: # ✓ CORRECT: constraints at root level
MOD:
regex: "fs"WRONG - duplicate not: keys:
rule:
all:
- pattern: $FUNC($$$ARGS)
- not: # ❌ First not
inside:
kind: await_expression
- not: # ❌ DUPLICATE KEY - YAML will only keep one!
inside:
kind: return_statementRIGHT - wrap in all: with separate patterns:
rule:
all:
- pattern: $FUNC($$$ARGS)
- not:
inside:
kind: await_expression
stopBy: end
- not:
inside:
kind: return_statement
stopBy: endOr use any: for alternatives:
rule:
any:
- pattern: fetch($$$)
- pattern: axios.$METHOD($$$)all: / any: StructurePattern: When you need multiple conditions or multiple negations, always wrap in all: or any:.
# Multiple conditions all must match
rule:
all:
- pattern: $FUNC($$$ARGS)
- has:
kind: call_expression
- not:
inside:
kind: await_expression
# Any of these patterns match
rule:
any:
- pattern: console.log($$$)
- pattern: console.warn($$$)
- pattern: console.error($$$)id: rule-id # Required: unique identifier
language: TypeScript # Required: target language
severity: error # Required: error, warning, hint, info
message: "Error message" # Required: user-facing message
files: # Optional: glob patterns
- src/**/*.ts
ignores: # Optional: exclusion patterns
- "**/*.test.ts"
rule: # Required: the matching rule
pattern: ... # Basic pattern
# OR
all: [] # Multiple conditions
# OR
any: [] # Alternative patterns
constraints: # Optional: variable constraints (TOP LEVEL!)
VAR_NAME:
regex: "pattern"
utils: # Optional: utility patterns
MY_UTIL:
pattern: ...Always validate your YAML structure before testing:
# Check YAML is valid
python3 -c "import yaml; yaml.safe_load(open('rules/my-rule.yml'))" && echo "YAML OK"
# Check rule structure
python3 scripts/validate-rule.py rules/my-rule.yml
# Then run ast-grep
cd rules/ast-grep && ast-grep scan| Error | Cause | Fix |
|---|---|---|
missing field constraints | constraints inside rule | Move to top level |
yaml.scanner.ScannerError | Duplicate keys | Use all: wrapper |
unknown variant | Invalid enum value | Check docs for valid values |
did not find expected key | Indentation error | Check YAML indentation |
Use this script to validate rule files before committing:
#!/usr/bin/env python3
"""Validate ast-grep rule YAML structure."""
import yaml
import sys
from pathlib import Path
def validate_rule(file_path):
"""Validate a single rule file."""
content = Path(file_path).read_text()
data = yaml.safe_load(content)
errors = []
# Check required fields
required = ['id', 'language', 'severity', 'message', 'rule']
for field in required:
if field not in data:
errors.append(f"Missing required field: {field}")
# Check constraints at wrong level (common mistake)
if 'rule' in data and isinstance(data['rule'], dict):
if 'constraints' in data['rule']:
errors.append("constraints inside rule: - must be at TOP LEVEL")
if 'utils' in data['rule']:
errors.append("utils inside rule: - must be at TOP LEVEL")
if 'transform' in data['rule']:
errors.append("transform inside rule: - must be at TOP LEVEL")
# Check for duplicate keys by analyzing raw YAML
lines = content.split('\n')
for i, line in enumerate(lines, 1):
stripped = line.lstrip()
if stripped.startswith('- '):
continue # Skip list items
if ':' in stripped:
key = stripped.split(':')[0]
# This is a simple check - proper parsing would be more robust
if errors:
print(f"❌ {file_path}")
for err in errors:
print(f" - {err}")
return False
else:
print(f"✓ {file_path}")
return True
if __name__ == "__main__":
if len(sys.argv) < 2:
print("Usage: validate-rule.py <rule-file.yml> [rule-file2.yml ...]")
sys.exit(1)
all_valid = True
for path in sys.argv[1:]:
if not validate_rule(path):
all_valid = False
sys.exit(0 if all_valid else 1)Save as scripts/validate-rule.py and run:
python3 scripts/validate-rule.py rules/*.ymlAdd this to .git/hooks/pre-commit or .pre-commit-config.yaml:
#!/bin/bash
# .git/hooks/pre-commit - validate ast-grep rules
RULES_DIR="rules/ast-grep/rules"
if [ -d "$RULES_DIR" ]; then
echo "Validating ast-grep rules..."
if ! python3 scripts/validate-rule.py "$RULES_DIR"/*.yml; then
echo ""
echo "❌ Rule validation failed. Fix YAML structure errors before committing."
echo " See skills/ast-grep-setup/SKILL.md for YAML structure rules."
exit 1
fi
fi
exit 0Make it executable:
chmod +x .git/hooks/pre-commitAdd this job to validate rules in CI:
# .github/workflows/validate-ast-grep-rules.yml
name: Validate ast-grep Rules
on: [push, pull_request]
jobs:
validate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Python
uses: actions/setup-python@v5
with:
python-version: "3.11"
- name: Install pyyaml
run: pip install pyyaml
- name: Validate rule files
run: python3 scripts/validate-rule.py rules/ast-grep/rules/*.yml© alchemiststudiosDOTai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 12 other files (scripts) in skills/ast-grep-setup of alchemiststudiosDOTai/harness-engineering.
Open the folder on GitHubat commit 7a9fa15
Ast Grep Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ast Grep Setup this skillalchemiststudiosDOTai/harness-engineering | 105 | — | ~4.7k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.3k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Eslint Migrate Optionsbiomejs/biome | 26k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Find Similar Functionsmillionco/react-doctor | 15k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Code Qualityredis/RedisInsight | 8.9k | — | ~1.2k | Automated safety check: Pass | Custom licence |
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
biomejs/biome
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
millionco/react-doctor
Use truffler to find similar or pre-existing JavaScript/TypeScript symbols before implementing new code, especially helpers, utilities, parsers, formatters, scanners, fuzzy matchers, and other…
redis/RedisInsight
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…
javierbrea/eslint-plugin-boundaries
Act as a software architect: analyze a repository's folder structure and cross-file import dependencies, detect its architectural pattern, design element/file boundaries with the user, and configure…
alchemiststudiosDOTai/harness-engineering
This skill should be used when mapping or researching a codebase to understand its structure, patterns, and architecture.
alchemiststudiosDOTai/harness-engineering
Execute implementation plans from .artifacts/plan/. An agent skill from alchemiststudiosDOTai/harness-engineering.
alchemiststudiosDOTai/harness-engineering
Map a repository's mechanical harness layers: canonical check command, local and CI gates, architecture boundaries, structural rules, behavioral verification, docs ratchets, evidence workflows, and…
alchemiststudiosDOTai/harness-engineering
This skill should be used when creating, refreshing, or validating a repository AGENTS.md so it stays concise, current, and grounded in repository evidence.
alchemiststudiosDOTai/harness-engineering
Run or continue a differential debugging session between two implementations, traces, captures, or outputs.
alchemiststudiosDOTai/harness-engineering
Generate execution-ready implementation plans from research docs - planning ONLY, no fixing or verifying.
Works with
Categories
Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs. Ast Grep Setup is an agent skill from alchemiststudiosDOTai/harness-engineering. Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs.
Ast Grep Setup fits situations like: adding structural linting; banning legacy patterns; implementing ratchet gates.
Run `npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a claude-code`. Or copy the skill folder (skills/ast-grep-setup in alchemiststudiosDOTai/harness-engineering) into .claude/skills/ast-grep-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a codex`. Or copy the skill folder (skills/ast-grep-setup in alchemiststudiosDOTai/harness-engineering) into .agents/skills/ast-grep-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alchemiststudiosDOTai/harness-engineering --skill ast-grep-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ast-grep-setup, .gemini/skills/ast-grep-setup, .github/skills/ast-grep-setup and .opencode/skills/ast-grep-setup in your project.
Going by SKILL.md and its folder, Ast Grep Setup needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and node). Our summary lists: Python 3; Node.js.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Ast Grep Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ast Grep Setup: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Eslint Migrate Options (biomejs/biome, 26k stars), Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars) and Find Similar Functions (millionco/react-doctor, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
alchemiststudiosDOTai (a GitHub organization) maintains it in alchemiststudiosDOTai/harness-engineering, which has 105 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on March 17, 2026.
Source: alchemiststudiosDOTai/harness-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.