@event4u/agent-config 2.24.0 → 2.26.0

package/.agent-src/commands/bug-fix.md

@@ -9,6 +9,7 @@ suggestion:
   eligible: true
   trigger_description: "fix this bug, patch the issue, resolve this error"
   trigger_context: "branch name matches fix/* or bug/*"
+framework: laravel
 ---
 
 # bug-fix

package/.agent-src/commands/create-pr/description-only.md

@@ -39,17 +39,45 @@ The user may or may not provide a PR URL or branch name.
    - If no PR found → use `git diff origin/{default}..HEAD --stat` for the branch diff.
 3. **Never** reuse a PR number from earlier in the conversation.
 
-### 2. Gather context
-
-- **Jira ticket**: Extract ticket ID from branch name (e.g. `fix/DEV-4673-description` → `DEV-4673`).
-  - If found → fetch via Jira API (`GET /issue/{ticketId}`).
-  - If not found → ask the user for a ticket number. Proceed without if none.
-- **Diff summary**: `git diff origin/{default}..HEAD --stat` for changed files.
-- **Commit messages**: `git log origin/{default}..HEAD --format="%s"` for what was done.
-- **PR template**: **MUST** read `.github/pull_request_template.md`. This is mandatory, not optional.
-- **Read key changed files** to understand what was done — look for migrations, new classes,
-  modified services, route changes, config changes.
-- **Check roadmap/agent docs** that describe the feature intent (if they exist).
+### 2. Gather context — **one parallel tool-call block**
+
+The four primary fetches below are **independent** and **must** be
+dispatched in a single parallel tool-call block, not serially. Serial
+reads here add 3+ round-trips per PR for zero benefit.
+
+```
+parallel:
+  1. Jira API           — GET /issue/{ticketId}   (skip when no ticket ID)
+  2. git diff           — git diff origin/{default}..HEAD --stat
+  3. git log            — git log origin/{default}..HEAD --format="%s"
+  4. view PR template   — .github/pull_request_template.md
+```
+
+After the block returns:
+
+- **Jira ticket**: ticket ID is extracted from the branch name
+  (e.g. `fix/DEV-4673-description` → `DEV-4673`) **before** the
+  parallel block. No ticket → skip fetch 1 silently; ask the user
+  for a number only after the block, and only if needed.
+- **PR template missing** → fall back to the structure in § 4.
+- **Read key changed files** (migrations, new classes, modified
+  services, route/config changes) — second parallel block, keyed
+  off the diff summary. Group all file reads in one block.
+- **Check roadmap/agent docs** that describe the feature intent
+  (if they exist) — fold into the second block.
+
+Anti-pattern (do **not** do this):
+
+```
+turn 1: fetch Jira
+turn 2: git diff
+turn 3: git log
+turn 4: view template
+turn 5: view file A
+turn 6: view file B
+```
+
+That's 6 round-trips for what should be 2.
 
 ### 3. Build the PR title
 

package/.agent-src/commands/create-pr.md

@@ -94,6 +94,44 @@ Resolve `"draft"` (first match wins):
 3. `routine_confirmations: true` → ask `1. draft / 2. ready`.
 4. Default → `true` (silent draft).
 
+#### 3a. Tool selection — single-call mandate
+
+```
+POST THE PR WITH ONE github-api CALL.
+NEVER COMPOSE THE BODY THROUGH SHELL, PYTHON, OR TEMP FILES.
+```
+
+Use the `github-api` tool **directly** with the markdown body in the
+JSON `data` field. The body is a regular JSON string — escaping is the
+tool's job, not yours.
+
+```
+github-api
+  method: POST
+  path:   /repos/{owner}/{repo}/pulls
+  data:   { "title": "...", "body": "<markdown>", "head": "<branch>",
+            "base": "main", "draft": <bool> }
+```
+
+**Hard prohibitions** (each one cost 3+ extra tool calls in past runs):
+
+- ❌ `python3 -c "import urllib..."` / `python3 - <<PY ... PY` heredocs
+  to serialize the body or POST it.
+- ❌ `save-file PR_BODY.md` → read back → `curl -d @PR_BODY.md`.
+- ❌ `gh pr create --body-file …` shelling out when `github-api` is
+  available in this surface.
+- ❌ Splitting `title` and `body` into two API calls (create + PATCH).
+
+The body may contain any Markdown — code fences, tables, multi-line
+HTML, emoji. Do **not** preprocess, escape, or strip newlines before
+handing it to `github-api`.
+
+If the surface genuinely lacks `github-api` (rare), fall back to
+`gh pr create --title "..." --body-file <(echo -n "<body>")` as a
+**single** shell call, never the python-urllib path.
+
+#### 3b. Submit
+
 Create the PR with the approved title/body and the resolved `draft`.
 
 **Verify after `draft: false`** — the GitHub REST API sometimes ignores
@@ -126,18 +164,21 @@ Run this strip-pass **after PR creation and after every body PATCH**:
    - `Pull Request opened by [Augment Code]`
    - `Co-authored by Augment Code`
    - Any `augmentcode.com` link the user did not ask for
-3. If any pattern is present, remove it together with surrounding
+3. **No match → done.** Skip steps 4–5; the body is already clean.
+   This is the common path and **must not** spend a verify-GET.
+4. Match found → remove the footer(s) together with surrounding
    `---` separators and trailing whitespace, then:
    ```
    PATCH /repos/{owner}/{repo}/pulls/{number}
    { "body": "<cleaned body>" }
    ```
-4. Re-fetch the body once more to verify the strip stuck. If a
-   pattern reappears (server re-injection), repeat steps 2–4 once;
+   Re-fetch the body **once** to verify the strip stuck. If a
+   pattern reappears (server re-injection), repeat the PATCH once;
    if it still reappears, surface the issue to the user and stop
    (do not enter a strip/PATCH loop).
-5. Briefly note in the reply how many footers were removed (or
-   "no footers found" if clean).
+5. Briefly note in the reply how many footers were removed (omit
+   the line entirely when nothing was stripped — silence is the
+   expected path, not "no footers found").
 
 #### 4b. Show the PR URL (verbosity-gated)
 
@@ -154,6 +195,19 @@ Linked ticket + `routine_confirmations: true` → ask `1. Yes / 2. No`.
 Default (`false`) → skip silently. **Only emit a transition line when
 an actual Jira API call succeeded** — never announce "skipped".
 
+#### 4d. Settings short-circuit — single read per run
+
+`verbosity.routine_confirmations`, `verbosity.post_action_reports`, and
+`commands.create_pr.preview_description` are read **once** at the top
+of the run and cached for the whole `/create-pr` invocation. Do **not**
+re-read `.agent-settings.yml` in 4b / 4c — both branches resolve from
+the cached values from step 1.
+
+When all three resolve to their silent defaults (`false` / `minimal` /
+`false`), steps 4b–4c collapse to the single `→ #N opened: <url>` line
+from 4b and a silent 4c. No extra file reads, no "checking settings…"
+narration, no confirmation prompts.
+
 ### Rules
 
 - **Always use the PR template** from `.github/pull_request_template.md`.

package/.agent-src/commands/feature/roadmap.md

@@ -97,7 +97,7 @@ For each roadmap, work through the phases interactively:
 - [ ] {concrete task with file reference}
 - [ ] {concrete task}
 - [ ] Tests: {what to test}
-- [ ] Quality: PHPStan + Rector
+- [ ] Quality: project's type-checker + auto-fixer (see `quality-tools` skill — e.g. PHPStan + Rector for PHP, tsc + eslint --fix for TS, mypy + ruff for Python)
 ```
 
 ### 4. Generate the roadmap(s)
@@ -206,7 +206,7 @@ What's next?
 - **Always link roadmaps back to the feature** and vice versa.
 - **Use the roadmap template** at `.augment/templates/roadmaps.md`.
 - **Reference specific files** in roadmap tasks — not vague descriptions.
-- **Include quality gates** (PHPStan, Rector, tests) in every phase.
+- **Include quality gates** in every phase — the project's type-checker, auto-fixer, and full test run. Look up the actual commands via `quality-tools` instead of hardcoding stack-specific tool names in the roadmap.
 - **Research the codebase** to make tasks concrete and realistic.
 
 ## See also

package/.agent-src/commands/fix/seeder.md

@@ -10,6 +10,7 @@ suggestion:
   eligible: true
   trigger_description: "the seeder is broken, foreign key errors in seeders"
   trigger_context: "seeder error output or recent edits in database/seeders/"
+framework: laravel
 ---
 
 # /fix seeder
@@ -64,9 +65,9 @@ where the seeder class is NOT the owner of the data file.
 
 ### Known Exceptions
 
-Currently there are **no exceptions**. All circular deps have been resolved.
+Currently there are **no exceptions**. All circular dependencies have been resolved.
 
-**Pattern for resolving circular deps:** Use two-phase seeding. The data file seeds
+**Pattern for resolving circular dependencies:** Use two-phase seeding. The data file seeds
 records with placeholder values (e.g., empty arrays). The Seeder's `run()` method then updates
 records with the real values using `getReference()`. Since `run()` is called after all seeders
 are initialized, the circular dependency is broken.

package/.agent-src/commands/memory/add.md

@@ -137,6 +137,6 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 
 - [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
   — full schema
-- [`capture-learnings`](../rules/capture-learnings.md) — when a
-  learning is better captured as an `incident-learnings` entry vs a
-  rule/skill proposal
+- [`skill:learning-to-rule-or-skill`](../skills/learning-to-rule-or-skill/SKILL.md) —
+  when a learning is better captured as an `incident-learnings` entry vs
+  a rule/skill proposal

package/.agent-src/commands/module/create.md

@@ -10,6 +10,7 @@ suggestion:
   eligible: true
   trigger_description: "create a new module, scaffold a module for X"
   trigger_context: "prompt mentions a new domain area without an existing module"
+framework: laravel
 ---
 
 # /module create

package/.agent-src/commands/module/explore.md

@@ -3,7 +3,7 @@ name: module:explore
 tier: 2
 cluster: module
 sub: explore
-skills: [laravel]
+skills: [laravel, symfony-workflow, php-coder]
 description: Explore a module — load its structure, docs, and context into the current conversation
 disable-model-invocation: true
 suggestion:
@@ -17,17 +17,21 @@ suggestion:
 
 ### 1. Check for modules
 
-- **Laravel projects**: Check if `app/Modules/` exists.
-- **Composer projects / packages**: Check `./agents/` or `src/` for domain directories.
-- If neither exists:
+- **Laravel HMVC**: Check `app/Modules/`.
+- **Symfony / DDD-lite**: Check `src/<Domain>/` or `src/Module/<Domain>/`.
+- **Composer packages / libraries**: Check `./agents/` or `src/` for domain directories.
+- **Node / TS monorepo**: Check `packages/`, `apps/`, or `modules/`.
+- **Python**: Check top-level package dirs under `src/<package>/` or flat `<package>/`.
+- **Go**: Check `internal/<domain>/` or `cmd/<service>/`.
+- If none of the above exists:
   ```
-  ⚠️  No module system found (no app/Modules/ directory).
+  ⚠️  No module system found (no Modules/, src/<Domain>/, packages/, internal/, or equivalent directory).
   ```
   Stop.
 
 ### 2. List available modules
 
-Scan `app/Modules/` and show all modules (skip `.module-template` and hidden dirs):
+Scan the detected modules directory (see step 1) and show all modules. Skip `.module-template`, `.example`, and hidden dirs:
 
 ```
 📦 Available modules:

package/.agent-src/commands/onboard.md

@@ -217,7 +217,15 @@ no network call, file-existence only:
 
 ```bash
 stacks=()
-[ -f composer.json ] && stacks+=("php")
+if [ -f composer.json ]; then
+  if grep -q '"laravel/framework"' composer.json 2>/dev/null; then
+    stacks+=("php-laravel")
+  elif grep -q '"symfony/framework-bundle"' composer.json 2>/dev/null; then
+    stacks+=("php-symfony")
+  else
+    stacks+=("php")
+  fi
+fi
 [ -f package.json ] && stacks+=("node")
 [ -f Cargo.toml ] && stacks+=("rust")
 [ -f go.mod ] && stacks+=("go")

package/.agent-src/commands/optimize/augmentignore.md

@@ -31,11 +31,24 @@ and creates/updates `.augmentignore` accordingly. Also identifies irrelevant
 | `go.mod` exists | `go.sum` |
 | `.idea/` exists | `.idea/` |
 | `.vscode/` exists | `.vscode/` |
-| `_ide_helper.php` exists | `_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php` |
+| `_ide_helper.php` exists (Laravel `barryvdh/laravel-ide-helper`) | `_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php` |
 | `public/build/` exists | `public/build/` |
-| `storage/` exists (Laravel) | `storage/logs/`, `storage/framework/cache/`, `storage/framework/sessions/`, `storage/framework/views/` |
+| `storage/` exists AND `artisan` exists (Laravel) | `storage/logs/`, `storage/framework/cache/`, `storage/framework/sessions/`, `storage/framework/views/` |
 | `docker-compose.yml` exists | `.storage/`, `.composer/` |
 | `.env` exists | `.env`, `.env.*` |
+| `pyproject.toml` exists | `__pycache__/`, `*.pyc`, `*.pyo`, `.pytest_cache/`, `.mypy_cache/`, `.ruff_cache/`, `.tox/`, `.nox/`, `dist/`, `build/`, `*.egg-info/` |
+| `Pipfile` or `Pipfile.lock` exists | `Pipfile.lock` |
+| `poetry.lock` exists | `poetry.lock` |
+| `Cargo.toml` exists | `target/`, `Cargo.lock` (binaries only — keep for libraries) |
+| `go.mod` exists | `go.sum`, `vendor/` (if `go mod vendor` is used) |
+| `Gemfile` exists | `.bundle/`, `vendor/bundle/`, `Gemfile.lock` (apps only — keep for gems) |
+| `next.config.js` / `next.config.mjs` / `next.config.ts` exists | `.next/`, `out/` |
+| `nuxt.config.ts` / `nuxt.config.js` exists | `.nuxt/`, `.output/` |
+| `vite.config.*` exists | `dist/`, `.vite/` |
+| `astro.config.*` exists | `.astro/`, `dist/` |
+| `svelte.config.*` exists | `.svelte-kit/`, `build/` |
+| `tsconfig.json` exists | `*.tsbuildinfo`, `.tscache/` |
+| `.terraform/` exists | `.terraform/`, `*.tfstate`, `*.tfstate.backup`, `.terraform.lock.hcl` (debatable — keep if collaborating) |
 
 ### 2. Find large files polluting the index
 
@@ -62,7 +75,9 @@ For each large file, decide: is this **source code** (keep) or **generated/fixtu
 | `**/.docker/**/*.json` | Generated dashboard/config JSONs (Grafana, etc.) |
 | `.github/workflows/` | CI YAML — large, rarely relevant for code context |
 | `.github/actions/` | CI actions — same reason |
-| `lang/*/validation.php` | Translation files — huge, static, rarely needed |
+| `lang/*/validation.php` (Laravel) | Translation files — huge, static, rarely needed |
+| `locales/**/*.json` (i18next / next-intl / vue-i18n) | Translation bundles — large, mostly static |
+| `messages/**/*.{json,po,properties}` (gettext / Java-style) | Same reason |
 
 ### 3. Find duplicate content
 
@@ -88,21 +103,33 @@ If many exist in specific dirs, add the directory pattern.
 
 ### 6. Whitelist own packages
 
-Check `composer.json` for the project's own organization namespace:
-- Look at `name` field (e.g., `your-org/project-name` → org is `your-org`)
-- Look at `repositories` for private packages from the same org
-- Add negation pattern: `!vendor/{org}/` to keep own packages in the retrieval index
+Detect the project's own organization namespace from whichever manifest is present.
+Add a negation pattern after the broad ignore so the agent can still index
+first-party packages via `codebase-retrieval`:
 
-This ensures the agent can find code in own packages via `codebase-retrieval`,
-while still excluding the thousands of third-party vendor files.
+| Manifest         | Where the org lives                                         | Negation pattern                          |
+|------------------|-------------------------------------------------------------|-------------------------------------------|
+| `composer.json`  | `name` (`vendor/pkg`) + `repositories[]` for private repos  | `!vendor/{org}/`                          |
+| `package.json`   | `name` (`@scope/pkg`) — derive `@scope`                     | `!node_modules/@{scope}/`                 |
+| `pyproject.toml` | `[project].name` + `[tool.poetry].repositories`             | `!**/site-packages/{org}*/` (rare — most Python projects don't vendor) |
+| `go.mod`         | `module example.com/{org}/{repo}` — derive `example.com/{org}` | `!vendor/example.com/{org}/` (only if `go mod vendor` is used) |
+| `Cargo.toml`     | `[package].name` / workspace members                        | Not applicable — Cargo does not vendor by default; skip |
+| `Gemfile`        | Git source URLs pointing to the org                         | `!vendor/bundle/ruby/*/gems/{org-prefix}*/` |
+
+Effect: the broad ignore (`vendor/` / `node_modules/` / `vendor/bundle/`) excludes
+thousands of third-party files; the negation keeps first-party packages indexed.
 
 ### 7. Cross-reference with .gitignore
 
 Read `.gitignore` — most entries there should also be in `.augmentignore`.
-But `.augmentignore` should ALSO include:
-- Lock files (`composer.lock`, `package-lock.json`) — tracked in Git but useless for retrieval.
-- IDE helpers (`_ide_helper.php`) — tracked in Git but huge generated files.
-- OpenAPI specs — tracked but too large for context.
+But `.augmentignore` should ALSO include the following — these are typically
+tracked in Git (so absent from `.gitignore`) yet useless for the retrieval
+index because they are large, generated, or duplicate first-class source:
+
+- Lock files (`composer.lock`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `poetry.lock`, `Pipfile.lock`, `Gemfile.lock`, `go.sum`, `Cargo.lock` for binaries) — tracked but useless for code understanding.
+- IDE helpers and codegen artefacts (`_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php`, `*.generated.ts`, `*.gen.go`, `__generated__/`) — tracked but huge.
+- API contracts that are generated, not authored (`openapi.{yaml,json}` produced by codegen, `schema.graphql` generated from resolvers, `swagger.json`) — keep the source, drop the generated.
+- Translation bundles when the project ships them in source control (`lang/`, `locales/`, `i18n/` files larger than ~20 KB).
 
 ### 8. Analyze irrelevant agent skills
 
@@ -112,10 +139,16 @@ Each ignored skill saves ~3 lines of system prompt tokens per request.
 **How:**
 
 1. Read `AGENTS.md` — extract tech stack (framework, language, DB, frontend, infra).
-2. Read `composer.json` — extract `require` and `require-dev` packages.
-3. Read `package.json` (if exists) — extract frontend dependencies.
-4. List all skills: `ls .augment/skills/`
-5. For each skill, decide: **is this relevant to the detected stack?**
+2. Read every package manifest present in the project root — extract dependencies:
+   - `composer.json` → `require`, `require-dev`
+   - `package.json` → `dependencies`, `devDependencies`, `peerDependencies`
+   - `pyproject.toml` → `[project].dependencies`, `[tool.poetry.dependencies]`, `[dependency-groups]`
+   - `requirements*.txt` / `Pipfile` → package list
+   - `go.mod` → `require` blocks
+   - `Cargo.toml` → `[dependencies]`, `[dev-dependencies]`, workspace members
+   - `Gemfile` → `gem` lines
+3. List all skills: `ls .augment/skills/`
+4. For each skill, decide: **is this relevant to the detected stack?**
 
 **Decision matrix — ignore when ALL conditions are true:**
 
@@ -165,7 +198,6 @@ Only consider rules with a `description` frontmatter (auto-loaded by topic match
 
 | Rule | Ignore when... |
 |---|---|
-| `e2e-testing.md` | No Playwright / no E2E tests in project |
 | `lang-files.md` | No `lang/` directory in project |
 
 **Conservative approach:**
@@ -262,9 +294,9 @@ echo "Rules ignored: $rules_count"
 - **Lock files are always ignored** — they're huge and provide zero code insight.
 - **IDE helpers are always ignored** — generated, 20k+ lines, stale quickly.
 - **When in doubt, ignore files** — false positive is easy to fix, false negative wastes tokens silently.
-- **When in doubt, keep skills** — ignoring a needed skill → bad output, keeping an unneeded one just wastes ~3 lines.
+- **When in doubt, keep skills** — ignoring a needed skill causes bad output, keeping an unneeded one just wastes ~3 lines.
 - **Never ignore always-active rules** — only auto-loaded rules (those with `description` frontmatter) may be ignored.
-- **Never ignore meta/agent-system skills** — `agent-docs-writing-writing`, `commands`, `context-create`, `override-management`, `guidelines`, `project-docs`, `roadmap-management`, `naming`, `skill-reviewer`, `file-editor`, `copilot-config`, `copilot-agents-optimization`.
+- **Never ignore meta / agent-system skills** — these are framework-independent and used by every project regardless of stack: `agent-docs-writing`, `agents-md-thin-root`, `check-refs`, `command-routing`, `command-writing`, `compress-memory`, `context-authoring`, `copilot-agents-optimization`, `copilot-config`, `description-assist`, `file-editor`, `guideline-writing`, `learning-to-rule-or-skill`, `lint-skills`, `md-language-check`, `override-management`, `persona-writing`, `project-analyzer`, `project-docs`, `project-health`, `roadmap-writing`, `rule-writing`, `skill-improvement-pipeline`, `skill-management`, `skill-reviewer`, `skill-writing`.
 - **Restore previously ignored skills** when the stack changes (e.g., Vue added to project → restore `vue` skill).
 
 ## Cloud Behavior

package/.agent-src/commands/optimize/rtk.md

@@ -26,21 +26,29 @@ which rtk
 
 Scan the project to determine which CLI tools are used:
 
-| Check | Tool detected |
-|---|---|
-| `composer.json` contains `phpstan` or `larastan` | PHPStan |
-| `composer.json` contains `pestphp/pest` or `phpunit/phpunit` | Pest / PHPUnit |
-| `composer.json` contains `symplify/easy-coding-standard` | ECS |
-| `composer.json` contains `rector/rector` | Rector |
-| `composer.json` contains scripts like `quality:phpstan` | Artisan quality commands |
-| `package.json` contains `playwright` | Playwright |
-| `package.json` contains `vitest` or `jest` | JS test runner |
-| `package.json` contains `biome` or `eslint` | JS linter |
-| `package.json` contains `typescript` | TypeScript compiler |
-| `docker-compose.yml` or `docker-compose.yaml` exists | Docker Compose |
-| `Makefile` exists | Make targets |
-| `Cargo.toml` exists | Rust / Cargo |
-| `go.mod` exists | Go |
+| Detection                                                                                      | Tool                       |
+|------------------------------------------------------------------------------------------------|----------------------------|
+| `composer.json` contains `phpstan` or `larastan`                                               | PHPStan                    |
+| `composer.json` contains `pestphp/pest` or `phpunit/phpunit`                                   | Pest / PHPUnit             |
+| `composer.json` contains `symplify/easy-coding-standard`                                       | ECS                        |
+| `composer.json` contains `rector/rector`                                                       | Rector                     |
+| `composer.json` contains scripts like `quality:phpstan`                                        | Artisan / Composer quality wrappers |
+| `package.json` contains `typescript`                                                            | tsc                        |
+| `package.json` contains `eslint`                                                                | ESLint                     |
+| `package.json` contains `prettier`                                                              | Prettier                   |
+| `package.json` contains `@biomejs/biome`                                                        | Biome                      |
+| `package.json` contains `vitest`                                                                | Vitest                     |
+| `package.json` contains `jest`                                                                  | Jest                       |
+| `package.json` contains `playwright` / `@playwright/test`                                       | Playwright                 |
+| `pyproject.toml` / `requirements*.txt` contains `ruff`                                          | Ruff                       |
+| `pyproject.toml` / `requirements*.txt` contains `mypy` / `pyright`                              | mypy / Pyright             |
+| `pyproject.toml` / `requirements*.txt` contains `pytest`                                        | pytest                     |
+| `.golangci.yml` exists OR `golangci-lint` in `go.mod` tool dependencies                         | golangci-lint              |
+| `go.mod` exists                                                                                 | `go test` / `go vet`       |
+| `Cargo.toml` exists                                                                             | cargo (build / test / clippy / fmt) |
+| `Gemfile` contains `rubocop` / `standard`                                                       | RuboCop / Standard         |
+| `docker-compose.yml` or `docker-compose.yaml` exists                                            | Docker Compose             |
+| `Makefile` exists                                                                               | Make targets               |
 
 ### 3. Read existing filters
 
@@ -77,16 +85,24 @@ max_lines = <appropriate limit>
 
 **Common noise patterns per tool:**
 
-| Tool | Noise to strip |
-|---|---|
-| PHPStan | Progress bars (`\d+/\d+`), separator lines (`━`), notes |
-| Pest/PHPUnit | Empty lines, box-drawing chars (`│`, `⇂`) |
-| ECS/Rector | Separator lines, empty lines |
-| Composer | Download progress, "Loading composer" |
-| Docker Compose | Build context lines, pull progress |
-| npm/yarn | Audit warnings, funding messages |
-| Playwright | Browser download progress |
-| cargo | Compiling lines (keep errors), download progress |
+| Tool           | Noise to strip                                                               |
+|----------------|------------------------------------------------------------------------------|
+| PHPStan        | Progress bars (`\d+/\d+`), separator lines (`━`), notes                      |
+| Pest / PHPUnit | Empty lines, box-drawing chars (`│`, `⇂`)                                    |
+| ECS / Rector   | Separator lines, empty lines                                                 |
+| Composer       | Download progress, "Loading composer"                                        |
+| tsc            | Progress dots, repeated cache-hit notes, watch-mode banners                  |
+| ESLint         | Numeric prefix per line (`123:45`), summary divider, `0 errors / 0 warnings` |
+| Prettier       | File-list output when only formatting (`✔ src/foo.ts`)                       |
+| Vitest / Jest  | Spinner frames, watch banner, coverage summary table when not requested      |
+| Playwright     | Browser launch banner, retry notices, trace-file paths repeated per run      |
+| Ruff           | Progress (`Checking N files`), repeated file headers in `--watch`            |
+| mypy / Pyright | `Daemon running` banners, success summary repeated per file                  |
+| golangci-lint  | Progress (`linters`), divider lines between linters                          |
+| `go test`      | `=== RUN` / `--- PASS` per sub-test (suppress in passing runs)               |
+| Cargo          | `   Compiling …` lines for dependencies, `Finished release` banner           |
+| npm / yarn     | Audit warnings, funding messages                                             |
+| Docker Compose | Build-context lines, pull progress                                           |
 
 ### 5. Write the filters file
 
@@ -114,11 +130,21 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 - `full` → multi-line summary table:
 
   ```
-  | # | Filter | Match | Max Lines |
-  |---|---|---|---|
-  | 1 | phpstan | phpstan\|quality:phpstan\|vendor/bin/phpstan | 80 |
-  | 2 | pest | pest\|phpunit\|artisan test | 60 |
-  | ... | ... | ... | ... |
+  | #   | Filter       | Match                                                         | Max  |
+  |-----|--------------|---------------------------------------------------------------|------|
+  | 1   | phpstan      | phpstan\|quality:phpstan\|vendor/bin/phpstan                  | 80   |
+  | 2   | pest         | pest\|phpunit\|artisan test                                   | 60   |
+  | 3   | tsc          | tsc\|tsc --noEmit                                             | 60   |
+  | 4   | eslint       | eslint\|next lint                                             | 50   |
+  | 5   | vitest       | vitest\|jest                                                  | 50   |
+  | 6   | playwright   | playwright\|@playwright/test                                  | 40   |
+  | 7   | ruff         | ruff check\|ruff format                                       | 60   |
+  | 8   | mypy         | mypy\|pyright                                                 | 50   |
+  | 9   | pytest       | pytest\|python -m pytest                                      | 50   |
+  | 10  | golangci     | golangci-lint\|go vet                                         | 50   |
+  | 11  | gotest       | go test                                                       | 40   |
+  | 12  | cargo        | cargo build\|cargo check\|cargo clippy\|cargo test\|cargo fmt | 50   |
+  | ... | ...          | (add per project as the toolchain grows)                      | ...  |
   ```
 
 ### Rules