Skip to content
Back to search

entrix

MarketplaceWorks with Claude CodeGitHub

A Harness Engineering tool for turning quality rules, architecture constraints, and validation steps into executable guardrails.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/phodal--entrix/badge.svg)](/listings/phodal--entrix)

HTML

<a href="/listings/phodal--entrix"><img src="/api/listings/phodal--entrix/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Choose one installation path:

Claude Code Plugin (recommended)

/plugin marketplace add phodal/entrix
/plugin install entrix@entrix

Restart Claude Code after plugin installation.

Standalone CLI (`uv` or `pip`)

uv tool install entrix
# or
pip install entrix

entrix --help

If you want Claude Code MCP integration in the current repository after installing the CLI:

entrix install --repo .

Requires Python 3.10+. `uv` is only needed for the `uv` / `uvx` workflow.

<details> <summary><strong>What it does</strong></summary> <br>

- codify quality gates and architecture constraints as reusable guardrail specs - run checks by `fast` / `normal` / `deep` tiers - run change-aware checks on diffs with weighted scoring and hard gates - route risky changes to deeper validation with `review-trigger` - optionally add graph-based impact, test-radius, and review context analysis

</details>

<details> <summary><strong>Guardrails in the change lifecycle</strong></summary> <br>

- checks run before risky code lands - each run generates evidence - policy can hard-stop, warn, or escalate to human review automatically

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 25 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "entrix",
  3. "owner": {
  4. "name": "Phodal"
  5. },
  6. "plugins": [
  7. {
  8. "name": "entrix",
  9. "source": "./",
  10. "description": "Harness Engineering plugin exposing executable fitness functions for architecture quality, change-aware validation, and MCP-powered review context.",
  11. "version": "0.1.14",
  12. "author": {
  13. "name": "Phodal"
  14. },
  15. "category": "development",
  16. "tags": [
  17. "fitness",
  18. "quality",
  19. "mcp",
  20. "architecture",
  21. "code-review"
  22. ]
  23. }
  24. ]
  25. }
README.md · README · 728 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1 align="center">Entrix</h1>
  2. <p align="center">
  3. <strong>Shift quality from manual review to executable change guardrails.</strong>
  4. </p>
  5. <p align="center">
  6. <a href="https://pypi.org/project/entrix/">
  7. <img src="https://img.shields.io/pypi/v/entrix.svg" alt="PyPI version" />
  8. </a>
  9. <a href="https://pypi.org/project/entrix/">
  10. <img src="https://img.shields.io/pypi/pyversions/entrix.svg" alt="Python versions" />
  11. </a>
  12. <a href="https://opensource.org/licenses/MIT">
  13. <img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="MIT License" />
  14. </a>
  15. </p>
  16. <p align="center">
  17. <img src="https://raw.githubusercontent.com/phodal/entrix/main/docs/lifecycle.svg" alt="Entrix Lifecycle" width="85%" />
  18. </p>
  19. <br>
  20. ## Install
  21. Choose one installation path:
  22. ### Claude Code Plugin (recommended)
  23. ```bash
  24. /plugin marketplace add phodal/entrix
  25. /plugin install entrix@entrix
  26. ```
  27. Restart Claude Code after plugin installation.
  28. ### Standalone CLI (`uv` or `pip`)
  29. ```bash
  30. uv tool install entrix
  31. # or
  32. pip install entrix
  33. entrix --help
  34. ```
  35. If you want Claude Code MCP integration in the current repository after installing the CLI:
  36. ```bash
  37. entrix install --repo .
  38. ```
  39. Requires Python 3.10+. `uv` is only needed for the `uv` / `uvx` workflow.
  40. <details>
  41. <summary><strong>What it does</strong></summary>
  42. <br>
  43. - codify quality gates and architecture constraints as reusable guardrail specs
  44. - run checks by `fast` / `normal` / `deep` tiers
  45. - run change-aware checks on diffs with weighted scoring and hard gates
  46. - route risky changes to deeper validation with `review-trigger`
  47. - optionally add graph-based impact, test-radius, and review context analysis
  48. </details>
  49. <details>
  50. <summary><strong>Guardrails in the change lifecycle</strong></summary>
  51. <br>
  52. - checks run before risky code lands
  53. - each run generates evidence
  54. - policy can hard-stop, warn, or escalate to human review automatically
  55. </details>
  56. ## Lifecycle View
  57. ![Entrix Lifecycle](https://raw.githubusercontent.com/phodal/entrix/main/docs/lifecycle.svg)
  58. Additional design context:
  59. - `tools/entrix/docs/adr/README.md`: Entrix architecture decisions and rationale
  60. ## Terminology
  61. Entrix uses **fitness** in the evolutionary architecture sense: a fitness
  62. function is an executable check that measures whether a codebase still satisfies
  63. a quality or architecture goal. In product-facing language, you can think of
  64. these as versioned quality guardrails.
  65. ## Requirements
  66. - Python 3.10+
  67. - Git repository context for commands that use `--base HEAD~1`
  68. Optional:
  69. - `uv` for `uv tool install ...` and `uvx ...`
  70. - `pip install entrix[graph]` for graph commands
  71. ## Advanced Installation
  72. ### Alternate CLI Invocations
  73. <details>
  74. <summary><strong>CLI invocation options</strong></summary>
  75. <br>
  76. ```bash
  77. uv tool install entrix
  78. # or
  79. pip install entrix
  80. uvx entrix --help
  81. uvx entrix run --tier fast
  82. uvx entrix run --tier normal --stream failures
  83. uvx entrix run --tier normal --stream all
  84. uvx entrix review-trigger --base HEAD~1
  85. ```
  86. </details>
  87. <details>
  88. <summary><strong>Optional extras</strong></summary>
  89. <br>
  90. ```bash
  91. pip install entrix[graph]
  92. pip install entrix[mcp]
  93. pip install entrix[dev]
  94. uvx entrix install --repo .
  95. ```
  96. </details>
  97. ## First Run
  98. ### 1. Create a guardrail spec
  99. By default, `entrix run` looks for specs under the current project's:
  100. ```text
  101. docs/fitness/*.md
  102. ```
  103. When `docs/fitness/manifest.yaml` is present, Entrix uses the manifest as the
  104. source of truth. That allows nested evidence files such as
  105. `docs/fitness/runtime/observability.md` and `docs/fitness/runtime/performance.md`.
  106. Example `docs/fitness/code-quality.md`:
  107. ```yaml
  108. ---
  109. dimension: code_quality
  110. weight: 20
  111. threshold:
  112. pass: 90
  113. warn: 80
  114. metrics:
  115. - name: lint
  116. command: npm run lint 2>&1
  117. hard_gate: true
  118. tier: fast
  119. description: ESLint must pass
  120. - name: unit_tests
  121. command: npm run test:run 2>&1
  122. pattern: "Tests\\s+\\d+\\s+passed"
  123. hard_gate: true
  124. tier: normal
  125. description: unit tests must pass
  126. ---
  127. # Code Quality
  128. Narrative evidence, rules, and ownership notes can live below the frontmatter.
  129. ```
  130. ### Advanced metric fields
  131. Beyond the basic fields shown above, each metric in the frontmatter supports additional options:
  132. ```yaml
  133. metrics:
  134. - name: api_contract
  135. command: npm run test:contract 2>&1
  136. hard_gate: false
  137. tier: normal
  138. description: API contract tests
  139. # Execution scope — where this metric is authoritative
  140. # Values: local, ci, staging, prod_observation
  141. execution_scope: ci
  142. # Timeout in seconds (null = no limit)
  143. timeout_seconds: 120
  144. # Gate severity: hard, soft, advisory
  145. gate: soft
  146. # Evidence type: command, test, probe, sarif, manual_attestation
  147. evidence_type: test
  148. # Confidence level: high, medium, low, unknown
  149. confidence: high
  150. # Signal stability: deterministic, noisy
  151. stability: deterministic
  152. # Fitness kind: atomic (single check) or holistic (system-wide)
  153. kind: atomic
  154. # Analysis mode: static (code structure) or dynamic (runtime)
  155. analysis: dynamic
  156. # Owner responsible for this metric
  157. owner: team-platform
  158. # Only run when these file patterns change
  159. run_when_changed:
  160. - "src/api/**"
  161. - "openapi.yaml"
  162. # Temporary waiver to bypass a failing metric
  163. waiver:
  164. reason: "Known flaky test, fix tracked in issue #42"
  165. owner: team-platform
  166. tracking_issue: 42
  167. expires_at: "2025-06-01"
  168. ```
  169. ### 2. Run the checks
  170. ```bash
  171. entrix run --tier fast
  172. entrix run --tier normal
  173. entrix run --tier normal --scope ci --dimension code_quality --dimension testability
  174. entrix run --tier fast --metric eslint_pass --metric ts_typecheck_pass
  175. entrix run --changed-only --base HEAD~1
  176. entrix validate
  177. ```
  178. Use `--metric` when you want to run only specific metric names without creating a temporary dimension file split. Commands that use `--base HEAD~1` must run inside a git repository with a valid base revision.
  179. ### 3. Add review triggers
  180. By default, `review-trigger` loads the current project's:
  181. ```text
  182. docs/fitness/review-triggers.yaml
  183. ```
  184. Example `docs/fitness/review-triggers.yaml`:
  185. ```yaml
  186. review_triggers:
  187. - name: high_risk_directory_change
  188. type: changed_paths
  189. paths:
  190. - src/core/acp/**
  191. - src/core/orchestration/**
  192. - services/api/**
  193. severity: high
  194. action: require_human_review
  195. - name: oversized_change
  196. type: diff_size
  197. max_files: 12
  198. max_added_lines: 600
  199. max_deleted_lines: 400
  200. severity: medium
  201. action: require_human_review
  202. ```
  203. Run it:
  204. ```bash
  205. entrix review-trigger --base HEAD~1
  206. entrix review-trigger --base HEAD~1 --json
  207. ```
  208. Example output:
  209. ```json
  210. {
  211. "human_review_required": true,
  212. "base": "HEAD~1",
  213. "changed_files": [
  214. "services/api/src/routes/acp_routes.rs"
  215. ],
  216. "diff_stats": {
  217. "file_count": 13,
  218. "added_lines": 936,
  219. "deleted_lines": 20
  220. },
  221. "triggers": [
  222. {
  223. "name": "high_risk_directory_change",
  224. "severity": "high",
  225. "action": "require_human_review",
  226. "reasons": [
  227. "changed path: services/api/src/routes/acp_routes.rs"
  228. ]
  229. }
  230. ]
  231. }
  232. ```
  233. ### Develop from the Routa.js checkout
  234. If you are using the copy of `entrix` vendored in the Routa.js monorepo, the
  235. current repository workflow is:
  236. ```bash
  237. pip install -e tools/entrix
  238. PYTHONPATH=tools/entrix python3 -m entrix --help
  239. PYTHONPATH=tools/entrix python3 -m entrix run --tier fast
  240. PYTHONPATH=tools/entrix python3 -m entrix review-trigger --base HEAD~1
  241. ```
  242. Most local hooks and helper scripts in this repository use the
  243. `PYTHONPATH=tools/entrix python3 -m entrix ...` form so they can run directly
  244. from the monorepo checkout without requiring a separately installed global
  245. binary.
  246. ### Develop the package itself from source
  247. If you are working on the `entrix` package source itself, clone this repository and install it from the repository root.
  248. From the repository root:
  249. ```bash
  250. git clone https://github.com/phodal/entrix.git
  251. cd entrix
  252. uv pip install -e .
  253. ```
  254. With `pip`:
  255. ```bash
  256. git clone https://github.com/phodal/entrix.git
  257. cd entrix
  258. pip install -e .
  259. ```
  260. ## CLI Reference
  261. Most repositories only need these three commands:
  262. - `entrix run`: execute guardrail checks from `docs/fitness/*.md`
  263. - `entrix validate`: validate the guardrail configuration
  264. - `entrix review-trigger`: escalate risky diffs to human review
  265. Use `entrix analyze long-file` for oversized-file structure analysis and `entrix graph ...` for graph-backed impact analysis.
  266. ## Example Packs
  267. Entrix includes copyable examples under [`examples/`](./examples/):
  268. - [`examples/file-length-hook/`](./examples/file-length-hook/): pre-commit file budget hook
  269. - [`examples/frontend-quality-pack/`](./examples/frontend-quality-pack/): layered frontend quality gates with review-trigger guidance
  270. ### `entrix run`
  271. Runs dimension-based guardrail checks loaded from `docs/fitness/*.md`.
  272. Common flags:
  273. ```bash
  274. entrix run --tier fast
  275. entrix run --parallel
  276. entrix run --dry-run
  277. entrix run --verbose
  278. entrix run --format ascii
  279. entrix run --format rich
  280. entrix run --changed-only --base HEAD~1
  281. entrix run --files src/app.ts src/lib.ts
  282. entrix run --output report.json
  283. entrix run --output - # JSON to stdout
  284. entrix run --min-score 90
  285. ```
  286. Use `--output` to write a JSON report to a file (or `-` for stdout), useful for CI artifact collection. Use `--files` to pass an explicit list of changed files for incremental metric selection. Use `--format ascii` for a zero-dependency visual scorecard, or `--format rich` for richer terminal rendering when `rich` is installed (`pip install entrix[visual]`).
  287. ### `entrix install` / `entrix init`
  288. Generate `.mcp.json` for Claude Code MCP integration in a target repository.
  289. ```bash
  290. entrix install --repo .
  291. entrix init --dry-run
  292. ```
  293. ### `entrix serve`
  294. Run the Entrix MCP server over stdio.
  295. ```bash
  296. entrix serve
  297. ```
  298. ### `entrix validate`
  299. Checks that dimension weights sum to `100%`.
  300. ```bash
  301. entrix validate
  302. ```
  303. ### `entrix review-trigger`
  304. Evaluates governance-oriented trigger rules for risky changes.
  305. Common flags:
  306. ```bash
  307. entrix review-trigger --base HEAD~1
  308. entrix review-trigger --json
  309. entrix review-trigger --fail-on-trigger
  310. entrix review-trigger --config docs/fitness/review-triggers.yaml
  311. ```
  312. ### `entrix analyze long-file`
  313. Structural analysis for oversized or explicit source files. Returns ClassMap / FunctionMap payloads showing classes, methods, and standalone functions with line spans.
  314. Supported languages: Python, Rust, Go, Java, and TypeScript/JavaScript
  315. (including `tsx` / `jsx` files).
  316. ```bash
  317. entrix analyze long-file --files src/app.ts src/lib.ts
  318. entrix analyze long-file --json
  319. entrix analyze long-file --config file_budgets.json --strict-limit
  320. entrix analyze long-file --min-lines 100
  321. ```
  322. When no `--files` are given, the command auto-discovers files that exceed their configured line budget.
  323. ### `entrix graph ...`
  324. Graph-backed commands support building the code graph, querying relationships, impact analysis, test radius estimation, commit history analysis, and AI-friendly review context generation.
  325. Requires the optional graph dependency: `pip install entrix[graph]`.
  326. #### `entrix graph build`
  327. Build or update the code graph.
  328. ```bash
  329. entrix graph build --base HEAD~1
  330. entrix graph build --build-mode full --json
  331. ```
  332. #### `entrix graph stats`
  333. Show graph statistics (node and edge counts).
  334. ```bash
  335. entrix graph stats
  336. entrix graph stats --json
  337. ```
  338. #### `entrix graph impact`
  339. Analyze the blast radius of changed files.
  340. ```bash
  341. entrix graph impact --base HEAD~1
  342. entrix graph impact --base HEAD~1 --depth 3 --json
  343. ```
  344. #### `entrix graph test-radius`
  345. Estimate which tests are affected by changed files.
  346. ```bash
  347. entrix graph test-radius --base HEAD~1
  348. entrix graph test-radius --base HEAD~1 --max-targets 50 --json
  349. ```
  350. #### `entrix graph query`
  351. Run a structural query against the code graph.
  352. Available patterns: `callers_of`, `callees_of`, `imports_of`, `importers_of`, `children_of`, `tests_for`, `inheritors_of`, `file_summary`.
  353. ```bash
  354. entrix graph query callers_of "mymodule.MyClass.my_method"
  355. entrix graph query tests_for "src/core/engine.py" --json
  356. ```
  357. #### `entrix graph history`
  358. Estimate test radius for recent commits using the current graph.
  359. ```bash
  360. entrix graph history --count 20 --ref main
  361. entrix graph history --json
  362. ```
  363. #### `entrix graph review-context`
  364. Build an AI-friendly review context from the current graph.
  365. ```bash
  366. entrix graph review-context --base HEAD~1 --json
  367. entrix graph review-context --base HEAD~1 --max-files 20 --no-source
  368. entrix graph review-context --base HEAD~1 --output context.json
  369. ```
  370. ## Preset System
  371. Entrix uses a preset system to adapt behavior to different project layouts. The default `ProjectPreset` looks for guardrail specs in `docs/fitness/` and review triggers in `docs/fitness/review-triggers.yaml`.
  372. Custom presets can override:
  373. - `fitness_dir(project_root)` — where to find guardrail spec files
  374. - `review_trigger_config(project_root)` — path to the review trigger YAML
  375. - `should_ignore_changed_file(file_path)` — filter out irrelevant changed files
  376. - `domains_from_files(files)` — extract domain tags from changed file paths
  377. A built-in `RoutaPreset` is included as a reference implementation for monorepo layouts.
  378. ## AI-Friendly Authoring Notes
  379. If an AI agent is generating or updating guardrail specs, these conventions work best:
  380. - keep one dimension per file
  381. - make the frontmatter executable and the body explanatory
  382. - prefer stable command outputs over fragile text matching
  383. - use `hard_gate: true` only when failure should really block progress
  384. - keep review-trigger rules separate from scoring metrics
  385. - treat markdown as the narrative layer, not the only source of structure
  386. Recommended file layout:
  387. ```text
  388. your-project/
  389. docs/
  390. fitness/
  391. README.md
  392. manifest.yaml
  393. code-quality.md
  394. security.md
  395. runtime/
  396. observability.md
  397. performance.md
  398. review-triggers.yaml
  399. ```
  400. Minimal bootstrap flow for a new repository:
  401. ```bash
  402. mkdir -p docs/fitness
  403. cat > docs/fitness/code-quality.md <<'EOF'
  404. ---
  405. dimension: code_quality
  406. weight: 100
  407. threshold:
  408. pass: 100
  409. warn: 80
  410. metrics:
  411. - name: lint
  412. command: npm run lint 2>&1
  413. hard_gate: true
  414. tier: fast
  415. ---
  416. # Code Quality
  417. EOF
  418. entrix validate
  419. entrix run --tier fast
  420. ```
  421. Bootstrap authoring rules:
  422. - keep default local `entrix run` green on a fresh machine
  423. - if a command is authoritative only in CI or a provisioned environment, model
  424. it with `execution_scope: ci` instead of leaving it in the default local path
  425. - update every existing agent entry document consistently:
  426. `AGENTS.md`, `CLAUDE.md`, or both
  427. - if neither entry document exists, create only `AGENTS.md`
  428. Recommended bootstrap policy:
  429. - do not stop at a plausible draft; the bootstrap is done only after local
  430. `entrix validate` and plain local `entrix run` pass
  431. - keep default local runs backed by repo-safe wrappers or cheap smoke checks
  432. - move authoritative but provisioned checks into `execution_scope: ci`
  433. - treat `AGENTS.md` and `CLAUDE.md` discoverability as part of the bootstrap,
  434. not optional follow-up cleanup
  435. The repository also ships a bundled skill at `skills/entrix/` for agents that
  436. need to generate or repair `docs/fitness/` automatically. The skill follows the
  437. same bootstrap rules above and is validated against multiple real repositories.
  438. ## Skill Regression Harness
  439. The bundled `/entrix` skill ships with two regression modes:
  440. ```bash
  441. bash scripts/skill_regression.sh --fixtures
  442. bash scripts/skill_regression.sh /abs/path/to/repo-a /abs/path/to/repo-b
  443. ```
  444. - `--fixtures` validates bundled repository profiles under
  445. `tests/fixtures/skill_regression/`
  446. - path mode injects the bundled skill into each target repository, runs
  447. `claude -p /entrix`, then verifies the result with `entrix validate`,
  448. `entrix run --dry-run`, `entrix run --tier fast`, and plain `entrix run`
  449. Use fixture mode in CI and path mode for local forward validation against real
  450. repositories before publishing skill changes.
  451. ## Python API
  452. ### Review trigger example
  453. ```python
  454. from pathlib import Path
  455. from entrix.review_trigger import (
  456. collect_changed_files,
  457. collect_diff_stats,
  458. evaluate_review_triggers,
  459. load_review_triggers,
  460. )
  461. repo_root = Path(".").resolve()
  462. rules = load_review_triggers(repo_root / "docs" / "fitness" / "review-triggers.yaml")
  463. changed_files = collect_changed_files(repo_root, "HEAD~1")
  464. diff_stats = collect_diff_stats(repo_root, "HEAD~1")
  465. report = evaluate_review_triggers(rules, changed_files, diff_stats, base="HEAD~1")
  466. print(report.to_dict())
  467. ```
  468. ### Fitness spec loading example
  469. ```python
  470. from pathlib import Path
  471. from entrix.evidence import load_dimensions
  472. dimensions = load_dimensions(Path("docs/fitness"))
  473. for dimension in dimensions:
  474. print(dimension.name, len(dimension.metrics))
  475. ```
  476. ## Recommended Hook Integration
  477. For generic repositories, a practical pattern is:
  478. - `pre-commit`: run `entrix hook file-length` first, then quick lint
  479. - `pre-push`: run full checks, then print review-trigger warnings
  480. - CI: run `entrix run` and publish JSON/report output
  481. That lets automation catch deterministic failures early while still escalating ambiguous risky changes to humans.
  482. ### Current Routa.js hook layout
  483. The current Routa.js monorepo intentionally uses a slightly different split:
  484. - `pre-commit`: `npm run lint`
  485. - `post-commit`: `PYTHONPATH=tools/entrix python3 -m entrix hook file-length --config tools/entrix/file_budgets.pre_commit.json --strict-limit ...` as a warning-only budget report
  486. - `pre-push`: `./scripts/smart-check.sh`, which runs a curated `entrix run --metric ...` set and then evaluates `review-trigger`
  487. This keeps commit-time friction low while still surfacing file-budget drift and
  488. enforcing the higher-signal fitness gates before push.
  489. ## Submodule Bump Guidance
  490. If Entrix is vendored into a larger repository as a git submodule:
  491. - push the Entrix release commit first from a clean `tools/entrix` worktree
  492. - update the superproject pointer in its own commit
  493. - prefer a clean superproject branch or worktree for the pointer bump so
  494. unrelated application fitness hooks do not block a pure submodule update
  495. This keeps Entrix releases and superproject pointer bumps reviewable as separate
  496. changes.
  497. ### Reusable file-length guard
  498. `entrix` now exposes a reusable hook entrypoint:
  499. ```bash
  500. python3 -m entrix hook file-length \
  501. --config tools/entrix/file_budgets.pre_commit.json \
  502. --staged-only \
  503. --strict-limit
  504. ```
  505. Use it when you want AI-friendly oversized-file failures during `pre-commit`, for example:
  506. ```text
  507. current file length 2383 exceeds limit 1600: src/app/page.tsx
  508. ```
  509. A copy-pasteable template lives in [`examples/file-length-hook/`](examples/file-length-hook/).
  510. ## Project Status
  511. Current state:
  512. - stable for production use in real repository workflows
  513. - installable as a standalone PyPI package
  514. - suitable for AI-assisted project configuration
  515. Current boundaries:
  516. - the default authoring format is markdown frontmatter under `docs/fitness`
  517. - graph commands require the optional graph dependency: `pip install entrix[graph]`
  518. - the current public CLI in this checkout exposes `run`, `validate`, `review-trigger`, `hook`, `analyze`, and `graph`
  519. - `analyze long-file` structural analysis supports Python, Rust, Go, Java, TypeScript, and JavaScript
  520. - the internal architecture is still evolving toward a cleaner core / adapter / preset split
  521. ## Contributing
  522. See [CONTRIBUTING.md](CONTRIBUTING.md) for development guidelines and contribution workflow.
  523. ## License
  524. This project is licensed under the MIT License. See [LICENSE](LICENSE) for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.