Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

lint

/lint

Uruchamia pełną bramkę analizy statycznej dla Magento 2 (phpcs, phpstan, phpmd, php-cs-fixer, rector) na module lub diffie, stosuje bezpieczne poprawki i raportuje ręczne naruszenia w Markdown, JSON i SARIF.

Repozytorium
magento2-tools ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
10
Skrypty
5
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 5 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/apply-fixes.sh, scripts/build-findings.sh, scripts/exclude-lib.sh, scripts/run-analysis.sh, scripts/surface-invariants.sh

Co robi i kiedy

Uruchamia pełną bramkę analizy statycznej dla Magento 2 (phpcs, phpstan, phpmd, php-cs-fixer, rector) na module lub diffie, stosuje bezpieczne poprawki i raportuje ręczne naruszenia w Markdown, JSON i SARIF.

Wyzwalacze z opisu

fix coding-standard violationsmake this pass CI
Oryginalny opis (EN)

Run the project's full static-analysis gate (phpcs Magento2, phpstan, phpmd, php-cs-fixer, rector dry-run) over a module or diff and apply safe auto-fixes to green, listing manual-only violations as ranked findings (Markdown + JSON + SARIF). Use for 'fix coding-standard violations' / 'make this pass CI'. For an architecture/quality review WITHOUT fixing, use `magento2-tools:review`.

Jak działa

  1. Core Rules
  2. Workflow
  3. Reference Files
  4. Scripts
  5. Inputs
  6. Outputs
  7. Related Skills
Sekcje z nagłówków SKILL.md, w oryginale · 203 linii, 1 423 słów
Podgląd SKILL.md
---
name: lint
version: 1.4.1
description:
    Run the project's full static-analysis gate (phpcs Magento2, phpstan, phpmd,
    php-cs-fixer, rector dry-run) over a module or diff and apply safe auto-fixes to
    green, listing manual-only violations as ranked findings (Markdown + JSON + SARIF).
    Use for 'fix coding-standard violations' / 'make this pass CI'. For an
    architecture/quality review WITHOUT fixing, use `magento2-tools:review`.
---

# Magento 2 Static Analysis

Action skill — runs the project's static-analysis toolchain, applies safe auto-fixes,
and reports residual violations as ranked findings. Unlike `review`
(read-only, architecture-focused), this skill **modifies files** to green the CI gate.

## Core Rules

- **Probe tools via `{ctx.tools}`.** Skip any tool not present. NEVER install anything.
- **Fixers run ONLY after the Phase-2 approval gate.** No file is touched until the user
  explicitly types "proceed" (or an equivalent confirmation).
- **Safe transforms only.** `phpcbf` and `php-cs-fixer` are the only auto-applied fixers.
  They are purely mechanical and cannot change observable behaviour.
- **Rector is PROPOSED, not auto-applied.** Rector runs in `--dry-run` mode during Phase 2
  (detection only). Its findings are listed for manual review; the skill never applies rector
  transforms automatically. The developer applies any desired rector changes manually after
  reviewing the proposals.
- **Re-run after fixing.** After applying fixes, the analysis gate re-runs and reports
  the residual (manual-only) violations.
- **NEVER edit `vendor/`.** All fixers exclude the `vendor/` directory unconditionally.
- **Severity shared scale.** See `context/references/severity.md`.
- **Findings schema shared.** See `context/references/findings-schema.md`
  (`outputKind = quality`).
- **Coding standard.** The enforcement gate is `--standard=Magento2` phpcs. See
  `context/references/php-coding-style.md` for the full style rules.
- **Output budget.** Follow `context/references/output-budget.md` — targeted reads, summary-first test/lint output, long logs to files.

## Workflow

### Phase 0 — Context Resolution

Invoke `context`. Capture `{ctx}` — especially `{ctx.tools}` (which tools are
available) and `{ctx.runner}` (Docker vs bare PHP prefix). Abort with a clear error if
no PHP environment is found (`runner_kind` is `null`).

### Phase 1 — Scope

Determine which files to analyse. Three modes:

| Mode | Trigger |
|------|---------|
| Module | `--module=Acme_OrderExport` or a bare module name / path |
| Diff | `--diff [<ref>]` (default `origin/main`) — analyse only changed files |
| Explicit files | One or more file paths passed directly |

For module scope, resolve the absolute path via `{ctx.magento_root}/app/code/{Vendor}/{Module}`.
Exclude `vendor/`, `generated/`, `var/`, `pub/static/` unconditionally — **anchored at the scan
target** (`<target>/vendor/*`, …), never as free-floating `*/var/*` globs. PHP_CodeSniffer and PHPMD
match exclude patterns against each file's full real path, so `*/var/*` excludes everything under a
container's `/var/www/…` install root and `*/vendor/*` everything in a Composer-installed module:
the scanners check 0 files and the pass reads as clean. `scripts/exclude-lib.sh` builds the list
for both `run-analysis.sh` and `apply-fixes.sh`.

### Phase 2 — Analysis Pass + Fix Plan (GATE)

Run every available tool in **read-only / dry-run mode** using
`${CLAUDE_SKILL_DIR}/scripts/run-analysis.sh`. Aggregate violations into a findings
JSON array.

The pass also runs the **surface-invariant** rules (`category: surface`) — cross-file
completeness checks that need no external tool, so they run even where phpcs/phpstan are
absent. They catch the class of defect the tool-driven scanners structurally cannot: a surface
whose files are each individually valid but incomplete as a set (a queue topic with no
publisher, a grid collection without the SearchResult bridge, an ACL id re-declared under the
wrong parent — an admin lockout). Every rule came from a real bug report; see
`references/surface-invariants.md`. None of them are auto-fixable — each needs a decision about
which file to add or which type to change.

Present the fix plan to the user showing:

- Total violations found per tool
- Which violations are **auto-fixable** (phpcbf, php-cs-fixer, safe rector rules)
- Which violations are **manual-only** (phpstan level errors, phpmd, risky rector, and every
  `surface` finding)
- Estimated residual count after auto-fix
- Any `scanner_errors` entry — a scanner that degraded checked **nothing**, which is not the
  same as finding nothing. Surface rules that could not be decided report there by name.
- The `tools` status of each scanner — `executed`, `unavailable`, `skipped` or `degraded`. Only an
  `executed` scanner stands behind a zero count; phpcs is `degraded` when its report lists 0 files
  for a target that has PHP files.

**WAIT for the user to type "proceed" before changing any file.** This gate is
mandatory. A write skill that touches files without explicit approval is a defect.

### Phase 3 — Apply Safe Fixes

Run `${CLAUDE_SKILL_DIR}/scripts/apply-fixes.sh` with the approved scope. The script:

1. Runs `phpcbf --standard=Magento2` over the scope (auto-fixes PHPCS style violations).
2. Runs `php-cs-fixer fix` with safe rules if the tool is available.
3. Captures before/after violation counts.
4. Never touches files outside the approved scope; never touches `vendor/`.

Rector is NOT run by apply-fixes.sh. Rector proposals from Phase 2 are manual-only;
the developer applies them after reviewing each proposed transform.

### Phase 4 — Verify

Re-run `${CLAUDE_SKILL_DIR}/scripts/run-analysis.sh` on the same scope. Report:

- Residual violation count (manual-only findings that remain after auto-fix)
- Delta: violations resolved by auto-fix vs still open
- Confirmation that no new violations were introduced by the fixers
- Confirmation that `vendor/` was not touched

### Phase 5 — Report

Write three artifacts:

1. **Markdown** — narrative report saved to
   `{output_root}/quality/{Vendor}_{Module}-quality-{YYYY-MM-DD}.md` (module scope;
   site/diff scope: `quality-{scope}-{YYYY-MM-DD}.md`). Sections: scope summary,
   auto-fix summary (before/after counts), residual findings by severity/tool, proposed
   risky rector rules (manual action needed), skipped tools.
2. **JSON + SARIF** — built by `${CLAUDE_SKILL_DIR}/scripts/build-findings.sh` using
   `OUTPUT_KIND=quality`. Residual findings only (auto-fixed violations are excluded).
   Run `build-findings.sh` with `DOCS_ROOT=<output_root>` (the resolved `--docs-root`
   value, or `.docs` by default) so both artifacts land under `{output_root}/quality/`.

## Reference Files

- `references/tool-matrix.md` — which tool detects vs fixes what; run command for each.
- `references/surface-invariants.md` — the cross-file completeness rule pack (SI-01…SI-12): what
  each rule asserts, the bug report it came from, and the two false-positive classes to avoid
  when adding one.
- `references/autofix-safety.md` — safe vs review-required transforms.
- `references/ci-integration.md` — running as a CI gate; SARIF upload; `--diff` PR gating.
- `context/references/findings-schema.md` — finding shape, `outputKind=quality`.
- `context/references/severity.md` — shared severity scale.
- `context/references/php-coding-style.md` — the Magento2 coding standard rules.

## Scripts

- `${CLAUDE_SKILL_DIR}/scripts/run-analysis.sh` — orchestrates read-only tool passes;
  outputs findings JSON array.
- `${CLAUDE_SKILL_DIR}/scripts/surface-invariants.sh` — the tool-free cross-file completeness
  rules; module scope only (each rule reasons about one module's file set, so a site/diff run
  must invoke it per changed module). Run by `run-analysis.sh`; standalone-callable.
- `${CLAUDE_SKILL_DIR}/scripts/apply-fixes.sh` — runs safe fixers (phpcbf, php-cs-fixer
  only); never touches `vendor/`. Rector is never auto-applied.
- `${CLAUDE_SKILL_DIR}/scripts/exclude-lib.sh` — sourced by `run-analysis.sh` and
  `apply-fixes.sh`; builds the `vendor/`, `generated/`, `var/`, `pub/static/` exclude list
  anchored at the target's realpath as the runner sees it.
- `${CLAUDE_SKILL_DIR}/scripts/build-findings.sh` — assembles residual findings into the
  shared JSON+SARIF format using the `emit-findings.sh` pipeline (emit-json.sh /
  emit-sarif.sh) owned by the `context` hub.

## Inputs

```
/lint [--module=<Vendor>_<Module>] [--diff [<ref>]] [--scope=module|site] [--docs-root=<path>] [<files>...]
```

### Tool environment

| Var | Purpose |
|-----|---------|
| `PHPSTAN_CONFIG` | Config passed as `-c`. Auto-discovered nearest-first: `{TARGET_PATH}/phpstan.neon`, then `phpstan-devpath.neon`/`phpstan.neon` beside the target's parent, then the Magento root, then the cwd. **Without a config phpstan loads no bootstrap and no autoloader**, so every framework class reads as unknown — the pass then emits confident false positives that are indistinguishable from real ones. When nothing is found the run still happens, with a warning in `scanner_errors`. |
| `PHPSTAN_MEMORY_LIMIT` | Default `2G`. php.ini's usual 128M makes phpstan crash on a Magento codebase and return an empty, apparently-clean result. |
| `RECTOR_FORCE` | `1` runs rector even on a pairing known to be broken. |

**Rector 1.x is skipped on PHP ≥ 8.5.** It emits `ReflectionProperty::setAccessible()` deprecations
plus a stack trace for essentially every rule — measured at 495 MB of stderr on one module — and
never emits parseable JSON, so the pass contributes nothing while appearing to have run. Rector
**^2.5 runs clean on 8.5** (verified: valid JSON, zero bytes of stderr) and is *not* skipped, so the
guard is on the pairing rather than the PHP version. Note that adopting Rector 2.x requires
`phpstan/phpstan ^2.2`, so it implies the PHPStan 2.x migration — not a standalone bump.

## Outputs

Module scope (basename uses the underscore module name, e.g. `Acme_OrderExport`):
```
{output_root}/quality/{Vendor}_{Module}-quality-{date}.md    # Markdown narrative (LLM, Phase 5)
{output_root}/quality/{Vendor}_{Module}-quality-{date}.json  # JSON findings (build-findings.sh)
{output_root}/quality/{Vendor}_{Module}-quality-{date}.sarif # SARIF (build-findings.sh)
```
Site/diff scope:
```
{output_root}/quality/quality-{scope}-{date}.md
{output_root}/quality/quality-{scope}-{date}.json
{output_root}/quality/quality-{scope}-{date}.sarif
```
`{output_root}` defaults to `.docs` (`{ctx.docs_root}`); see the `--docs-root`/`DOCS_ROOT`
recipe in `context/references/artifact-layout.md`.

### Output root (`--docs-root`)

This skill accepts `--docs-root=<path>` (see
`context/references/artifact-layout.md`). When set, run the emitter with
`DOCS_ROOT=<path>` so artifacts land under `<path>/quality/`; otherwise they default
to `{ctx.docs_root}/quality/`. Orchestrators such as `feature`
pass this to collect a run's artifacts under one folder.

## Related Skills

| Skill | Relationship |
|-------|-------------|
| `review` | Architecture/quality review WITHOUT fixing — use when you want findings, not fixes |
| `context` | Supplies `{ctx.tools}`, `{ctx.runner}`, `{ctx.magento_root}` |
| `fix` | For defects found during analysis that require RCA rather than a style fix |
| `security` | Deeper security scan beyond coding-standard enforcement |
Pliki w paczce (10)
  • SKILL.md 11 KB
  • references/autofix-safety.md 5 KB
  • references/ci-integration.md 4 KB
  • references/surface-invariants.md 7 KB
  • references/tool-matrix.md 8 KB
  • scripts/apply-fixes.sh 7 KB
  • scripts/build-findings.sh 4 KB
  • scripts/exclude-lib.sh 2 KB
  • scripts/run-analysis.sh 30 KB
  • scripts/surface-invariants.sh 40 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · muon-m2/magento2-tools100MIT
RediSearch/RediSearch100AGPL-3.0
pmdevsolutions/aurelius100MIT
rvdbreemen/adr-kit100MIT
mehrad-dm/mastermind100MIT
rjroy/vibe-garden100MIT
arbazkhan971/godmode100MIT
plato-corp/skills100MIT
Zate/cc-plugins100MIT

Migawka bazy z 13.11.2026 · wersja paczki fae0f8dd39eb (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100php-quality-tooling
    Konfiguruje PHPStan, Rector i PHP-CS-Fixer w projekcie PHP bez Laravela, razem z podpięciem do CI.
  • 100php-quality
    Prowadzi analizę statyczną, styl kodu i idiomy PHP 8.3-8.5: phpstan.neon i baseline, PHPStan lub Psalm, PHP-CS-Fixer lub PHP_CodeSniffer, PER-CS, PSR-12 i zestawy Rector.
  • 100code-standards-checker
    Uruchamia po zmianach w kodzie właściwe polecenia lintowania, formatowania i analizy statycznej oraz sprawdza zgodność z PHPCS, ESLint, WordPress Coding Standards lub Drupal Coding Standards.
  • 90php-modernization
    Modernizuje kod PHP: funkcje PHP 8.1 do 8.5, zgodność z PSR i PER-CS, narzędzia PHPStan, Rector, PHP-CS-Fixer i PHPat, DTO, enumy, readonly, property hooks oraz bezpieczeństwo typów.
  • 100quality-tools
    Obsługuje wyniki PHPStan, Rector i ECS, w tym błędy typów, poprawki stylu kodu i uruchamianie rector, także w kodzie Eloquent i Laravel.
  • 100code-quality
    Obsługuje narzędzia jakości kodu PHP i Laravel: analiza statyczna Larastan i PHPStan, styl Pint, refaktoryzacja Rector, baseline dla starszych projektów i integracja z CI w GitHub Actions.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.