architecture-auditing-linterlisted

# Architecture Auditing (Linter) > *"Dont Trust, must verify."* It scans your code for violations of the architecture rules for logging, pathlib, print, etc. ### How to use? The `human-skills` linter accepts numerous tool arguments for different purposes. Below, all available arguments are explained: allowed_args = { "default": ["scan_path", "path", "ignored_path", "ignored_apth", "linter_type"], "rest_api": ["scan_path", "path", "ignored_path", "ignored_apth", "linter_type", "ignored_rules"] } ```json { "tool_name": "linter", "tool_args": { "scan_path": "Path to the project directory or a specific .py file to audit (REQUIRED).", "linter_type": "Linter mode: 'default' (architecture violations) or 'rest_api' (API quality score). Defaults to 'default'.", "ignored_path": "Comma-separated list of directory names to skip during scanning (e.g., 'venv, .git, tests').", "ignored_rules": "Comma-separated list of rules to skip. Works only in rest_api mode. Example: 'auth, rate_limiting, caching'." } } ``` #### 1. Audit entire project ```bash human-skills '{ "tool_name": "linter", "tool_args": { "linter_type": "default", "scan_path": "home/user_name/project/", "ignored_path": "venv, .git, tests, configs" } }' ``` #### 2. Audit rest api endpoint ```bash human-skills '{ "tool_name": "linter", "tool_args": { "linter_type": "rest_api", "scan_path": "home/user_name/project