@event4u/agent-config 1.16.0 → 1.18.0

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

@@ -1,89 +1,54 @@
 ---
 name: judge
-skills: [subagent-orchestration]
-description: Run a standalone judge on an existing diff or code change — no implementer, no revision loop, verdict only
+description: Judge orchestrator — routes to solo, steps, on-diff
+cluster: judge
 disable-model-invocation: true
 suggestion:
-  eligible: false
-  rationale: "Sibling of /review-changes — eligibility routed there; keep this explicit."
+  eligible: true
+  trigger_description: "judge this diff, review with verdict, run an implementer→judge loop, step-by-step judged execution"
+  trigger_context: "user wants a verdict on a diff, a do-and-judge loop, or a step-gated execution"
 ---
 
-# judge
+# /judge
 
-## Instructions
+Top-level orchestrator for the `/judge` family. Replaces 3 standalone
+commands with a single entry point + sub-command dispatch.
 
-### 1. Identify the target
+## Sub-commands
 
-The user invoked `/judge` on one of:
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/judge solo` | `commands/judge/solo.md` | Standalone verdict on an existing diff — no implementer, no revision loop |
+| `/judge on-diff` | `commands/judge/on-diff.md` | Implementer→judge loop on a single change with a two-revision ceiling |
+| `/judge steps` | `commands/judge/steps.md` | Execute an ordered plan step by step, judge gate between steps |
 
-- The current working-tree diff (`git diff`)
-- A specific commit range (`git diff A..B`)
-- A PR by number or URL
-- A single file or set of files
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+The standalone reviewer surface lives at [`/review`](review-changes.md).
 
-Confirm the target in one sentence before proceeding. Do not silently
-assume the working tree.
+## Dispatch
 
-### 2. Gather the context
+1. Parse the user's argument: `/judge <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions`
+   section verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and
+   ask:
 
-Collect what the judge needs:
+   > 1. solo — verdict only, no loop
+   > 2. on-diff — implementer→judge revision loop
+   > 3. steps — judge gate between ordered steps
 
-- The diff in full
-- The original task, ticket, or PR description
-- Relevant acceptance criteria (tests, linter config, design doc)
+## Rules
 
-If any of these is missing and the judgment would be shallow without
-it, **stop** and ask.
-
-### 3. Resolve the judge model
-
-Read `.agent-settings.yml`:
-
-- `subagents.judge_model` → empty = one tier above session model
-
-Unknown alias → stop. Silence is not a fallback.
-
-### 4. Invoke the judge
-
-The judge reviews the diff against the task. Return one of:
-
-| Verdict  | Meaning                                      |
-|----------|----------------------------------------------|
-| `apply`  | Correct, complete, ready to land             |
-| `revise` | Specific issues listed — user decides next   |
-| `reject` | Fundamentally wrong approach                 |
-
-Unlike `/do-and-judge`, this command does **not** loop — no revision
-cycles. The verdict is the deliverable.
-
-### 5. Report
-
-```
-Mode:    judge (standalone)
-Target:  <diff | commit range | PR #N | files>
-Judge:   <resolved model>
-Verdict: apply | revise | reject
-Issues:  <numbered list if revise/reject>
-Next step: <what the user should do based on the verdict>
-```
-
-## Use this command when
-
-- A diff already exists and the user wants a second opinion
-- Reviewing someone else's PR before approving it
-- Double-checking a change before opening a PR
-- Stress-testing a refactor without committing to revisions
-
-## Do NOT
-
-- NEVER apply the diff — this command judges only
-- NEVER loop into a revision cycle — use `/do-and-judge` for that
-- NEVER run the judge on an empty diff — fail fast
-- NEVER silently fall back to the session model for the judge
+- **Do NOT commit, push, or open a PR** unless the sub-command
+  explicitly authorizes it.
+- **Do NOT chain sub-commands.** One `/judge <sub>` per turn.
+- If the user invokes `/judge` with no argument, **show the menu** —
+  do not guess which sub-command they meant.
 
 ## See also
 
 - [`subagent-orchestration`](../skills/subagent-orchestration/SKILL.md)
-- [`/do-and-judge`](do-and-judge.md) — if a revision loop is wanted
-- [`/review-changes`](review-changes.md) — human-oriented self-review
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)
+- [`/review`](review-changes.md) — human-oriented self-review (Reviewer-mode contract)
+- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer)

package/.agent-src/commands/{memory-add.md → memory/add.md}

@@ -1,5 +1,7 @@
 ---
-name: memory-add
+name: memory:add
+cluster: memory
+sub: add
 description: Interactively add a validated entry to an engineering-memory file (domain-invariants, architecture-decisions, incident-learnings, product-rules)
 skills: [file-editor]
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "post-incident or post-decision conversation"
 ---
 
-# /memory-add
-
+# /memory add
 Creates or updates a single entry in one of the four engineering-memory
 YAML files under `agents/memory/` in the consumer project. The entry
 is validated against the schema in

package/.agent-src/commands/{memory-full.md → memory/load.md}

@@ -1,5 +1,7 @@
 ---
-name: memory-full
+name: memory:load
+cluster: memory
+sub: load
 description: Load ALL curated entries of a given memory type into the current context — opt-in full load for deep analysis, never auto-triggered
 skills: []
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "Description states 'never auto-triggered' — opt-in deep-load only."
 ---
 
-# /memory-full
-
+# /memory load
 Loads every entry of a single memory type into the current conversation
 as a formatted block. Use when the normal `memory_lookup` filter is too
 narrow and you need the full type for an architecture decision, audit,

package/.agent-src/commands/{memory-promote.md → memory/promote.md}

@@ -1,5 +1,7 @@
 ---
-name: memory-promote
+name: memory:promote
+cluster: memory
+sub: promote
 description: Promote an intake signal (or provisional proposal) into a curated memory entry — opens a PR and runs the admission gate.
 skills: [file-editor]
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "Curation pipeline — overlaps /memory-add; keep explicit."
 ---
 
-# /memory-promote
-
+# /memory promote
 Moves an entry from the provisional layer (intake JSONL) into the
 curated layer (`agents/memory/<type>.yml` or sharded). Promotion is
 gated by

package/.agent-src/commands/{propose-memory.md → memory/propose.md}

@@ -1,5 +1,7 @@
 ---
-name: propose-memory
+name: memory:propose
+cluster: memory
+sub: propose
 description: Append a provisional memory signal to the intake stream — the universal fallback for any producer (human or agent) to record a finding without committing to a curated entry.
 skills: [file-editor]
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "Programmatic intake fallback — overlaps /memory-add; keep explicit."
 ---
 
-# /propose-memory
-
+# /memory propose
 Drops a **signal** into `agents/memory/intake/signals-YYYY-MM.jsonl` via
 `scripts/memory_signal.py`. Signals are append-only JSONL and merge-safe.
 

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

@@ -0,0 +1,48 @@
+---
+name: memory
+description: Memory orchestrator — routes to add, load, promote, propose
+cluster: memory
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "add a memory entry, load all memories, promote a signal, propose a finding"
+  trigger_context: "user wants to write to or curate engineering memory"
+---
+
+# /memory
+
+Top-level orchestrator for the `/memory` family. Replaces 4 standalone
+commands with a single entry point + sub-command dispatch.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/memory add` | `commands/memory/add.md` | Interactively add a validated entry to a memory file |
+| `/memory load` | `commands/memory/load.md` | Load ALL curated entries of a given memory type into context |
+| `/memory promote` | `commands/memory/promote.md` | Promote an intake signal to a curated memory entry |
+| `/memory propose` | `commands/memory/propose.md` | Append a provisional signal to the intake stream |
+
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+
+## Dispatch
+
+1. Parse the user's argument: `/memory <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions` section
+   verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and ask:
+
+   > 1. add — write a curated entry interactively
+   > 2. load — load ALL entries of a type for deep analysis
+   > 3. promote — promote an intake signal to a curated entry
+   > 4. propose — drop a provisional signal into the intake stream
+
+## Rules
+
+- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
+  authorizes it.
+- **Do NOT chain sub-commands.** One `/memory <sub>` per turn.
+- If the user invokes `/memory` with no argument, **show the menu** — do
+  not guess which sub-command they meant.

package/.agent-src/commands/{module-create.md → module/create.md}

@@ -1,5 +1,7 @@
 ---
-name: module-create
+name: module:create
+cluster: module
+sub: create
 skills: [laravel]
 description: Create a new module from .module-template with interactive setup
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "prompt mentions a new domain area without an existing module"
 ---
 
-# module-create
-
+# /module create
 ## Instructions
 
 ### 1. Check for module support

package/.agent-src/commands/{module-explore.md → module/explore.md}

@@ -1,5 +1,7 @@
 ---
-name: module-explore
+name: module:explore
+cluster: module
+sub: explore
 skills: [laravel]
 description: Explore a module — load its structure, docs, and context into the current conversation
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "existing Modules/<Name>/ referenced in the prompt"
 ---
 
-# module-explore
-
+# /module explore
 ## Instructions
 
 ### 1. Check for modules

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

@@ -0,0 +1,44 @@
+---
+name: module
+description: Module orchestrator — routes to create, explore
+cluster: module
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "create a new module, explore an existing module"
+  trigger_context: "user wants to scaffold or load a module's docs and structure"
+---
+
+# /module
+
+Top-level orchestrator for the `/module` family. Replaces 2 standalone
+commands with a single entry point + sub-command dispatch.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/module create` | `commands/module/create.md` | Create a new module from `.module-template` |
+| `/module explore` | `commands/module/explore.md` | Load a module's structure, docs, and context into the conversation |
+
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+
+## Dispatch
+
+1. Parse the user's argument: `/module <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions` section
+   verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and ask:
+
+   > 1. create — scaffold a new module from the template
+   > 2. explore — load a module's docs and structure
+
+## Rules
+
+- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
+  authorizes it.
+- **Do NOT chain sub-commands.** One `/module <sub>` per turn.
+- If the user invokes `/module` with no argument, **show the menu** — do
+  not guess which sub-command they meant.

package/.agent-src/commands/{optimize-agents.md → optimize/agents.md}

@@ -1,5 +1,7 @@
 ---
-name: optimize-agents
+name: optimize:agents
+cluster: optimize
+sub: agents
 description: Audits agent infrastructure — measures token overhead, checks rule triggers, verifies AGENTS.md. Suggest only, never auto-apply.
 skills: [copilot-agents-optimization, agents-audit, agent-docs-writing, quality-tools]
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "audit agent infrastructure, tune the agent setup"
   trigger_context: "maintainer working on .augment/ files"
-superseded_by: optimize agents
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /optimize-agents is deprecated; use /optimize agents instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# /optimize-agents
-
+# /optimize agents
 Agent infrastructure audit: measure token overhead, check rule triggers, verify AGENTS.md, find stale references. **Suggest only — never auto-apply.**
 
 **Source of truth:** `.agent-src.uncompressed/` — never read or edit `.agent-src/` or `.augment/` directly.

package/.agent-src/commands/{optimize-augmentignore.md → optimize/augmentignore.md}

@@ -1,22 +1,17 @@
 ---
 skills: [agent-docs-writing]
-name: optimize-augmentignore
+name: optimize:augmentignore
+cluster: optimize
+sub: augmentignore
 description: Creates or updates .augmentignore based on the project's actual tech stack, large files, generated artifacts, and irrelevant agent skills/rules.
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Niche maintenance tool with no recurring NL trigger."
-superseded_by: optimize augmentignore
-deprecated_in: "1.15.0"
 ---
-
-> ⚠️  /optimize-augmentignore is deprecated; use /optimize augmentignore instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
 <!-- cloud_safe: noop -->
 
-# /optimize-augmentignore
-
+# /optimize augmentignore
 Scans the project to find files that waste tokens in Augment's retrieval index
 and creates/updates `.augmentignore` accordingly. Also identifies irrelevant
 `.augment/skills/` and `.augment/rules/` to exclude them from the system prompt.

package/.agent-src/commands/{optimize-rtk-filters.md → optimize/rtk.md}

@@ -1,20 +1,16 @@
 ---
-name: optimize-rtk-filters
+name: optimize:rtk
+cluster: optimize
+sub: rtk
 skills: [agent-docs-writing]
 description: Create or optimize project-local rtk filters based on the actual toolchain
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Niche maintenance tool with no recurring NL trigger."
-superseded_by: optimize rtk
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /optimize-rtk-filters is deprecated; use /optimize rtk instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# optimize-rtk-filters
-
+# /optimize rtk
 ## Instructions
 
 ### 1. Check rtk is installed

package/.agent-src/commands/{optimize-skills.md → optimize/skills.md}

@@ -1,5 +1,7 @@
 ---
-name: optimize-skills
+name: optimize:skills
+cluster: optimize
+sub: skills
 description: Audits skills — measures baseline, finds duplicates/merge candidates, runs linter. Suggest only, never auto-apply.
 skills: [skill-reviewer]
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "audit my skills, find duplicate skills"
   trigger_context: "maintainer working on .augment/skills/ files"
-superseded_by: optimize skills
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /optimize-skills is deprecated; use /optimize skills instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# /optimize-skills
-
+# /optimize skills
 Skill audit: measure, find duplicates/merge candidates, run linter, present findings. **Suggest only — never auto-apply.**
 
 **Source of truth:** `.agent-src.uncompressed/` — never read or edit `.agent-src/` or `.augment/` directly.

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

@@ -18,10 +18,10 @@ commands with a single entry point + sub-command dispatch.
 
 | Sub-command | Routes to | Purpose |
 |---|---|---|
-| `/optimize skills` | `optimize-skills.md` | Audit skills — measure baseline, find duplicates, run linter |
-| `/optimize agents` | `optimize-agents.md` | Audit agent infrastructure — token overhead, rule triggers, AGENTS.md |
-| `/optimize augmentignore` | `optimize-augmentignore.md` | Create or refine `.augmentignore` based on actual stack |
-| `/optimize rtk` | `optimize-rtk-filters.md` | Create or refine project-local rtk filters |
+| `/optimize skills` | `commands/optimize/skills.md` | Audit skills — measure baseline, find duplicates, run linter |
+| `/optimize agents` | `commands/optimize/agents.md` | Audit agent infrastructure — token overhead, rule triggers, AGENTS.md |
+| `/optimize augmentignore` | `commands/optimize/augmentignore.md` | Create or refine `.augmentignore` based on actual stack |
+| `/optimize rtk` | `commands/optimize/rtk.md` | Create or refine project-local rtk filters |
 
 Sub-command names match the locked contract in
 [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
@@ -39,12 +39,6 @@ Sub-command names match the locked contract in
    > 3. augmentignore — create or refine `.augmentignore`
    > 4. rtk — create or refine project-local rtk filters
 
-## Migration
-
-The 4 standalone `/optimize-*` commands continue to work for one release
-cycle as deprecation shims. They emit a notice and route to the same
-content. New invocations should use `/optimize <sub>`.
-
 ## Rules
 
 - **Suggest only — never auto-apply.** All `/optimize` sub-commands are

package/.agent-src/commands/{override-create.md → override/create.md}

@@ -1,5 +1,7 @@
 ---
-name: override-create
+name: override:create
+cluster: override
+sub: create
 description: Creates a project-level override for a shared skill, rule, or command.
 skills: [override-management, agent-docs-writing]
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "prompt names a shared skill/rule needing project-specific behavior"
 ---
 
-# /override-create
-
+# /override create
 Creates an override file in `agents/overrides/` for a shared `.augment/` resource.
 
 ## Steps

package/.agent-src/commands/{override-manage.md → override/manage.md}

@@ -1,5 +1,7 @@
 ---
-name: override-manage
+name: override:manage
+cluster: override
+sub: manage
 description: Reviews, updates, and refactors existing project-level overrides.
 skills: [override-management, agent-docs-writing]
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "existing entries under agents/overrides/"
 ---
 
-# /override-manage
-
+# /override manage
 Manages existing overrides in `agents/overrides/`.
 
 ## Steps

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

@@ -0,0 +1,44 @@
+---
+name: override
+description: Override orchestrator — routes to create, manage
+cluster: override
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "create an override, manage existing overrides, refactor an override"
+  trigger_context: "user wants to add or curate project-level overrides under agents/overrides/"
+---
+
+# /override
+
+Top-level orchestrator for the `/override` family. Replaces 2 standalone
+commands with a single entry point + sub-command dispatch.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/override create` | `commands/override/create.md` | Create a project-level override for a shared skill, rule, or command |
+| `/override manage` | `commands/override/manage.md` | Review, update, and refactor existing overrides |
+
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+
+## Dispatch
+
+1. Parse the user's argument: `/override <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions` section
+   verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and ask:
+
+   > 1. create — author a new project-level override
+   > 2. manage — review, update, refactor existing overrides
+
+## Rules
+
+- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
+  authorizes it.
+- **Do NOT chain sub-commands.** One `/override <sub>` per turn.
+- If the user invokes `/override` with no argument, **show the menu** — do
+  not guess which sub-command they meant.

package/.agent-src/commands/{roadmap-create.md → roadmap/create.md}

@@ -1,5 +1,7 @@
 ---
-name: roadmap-create
+name: roadmap:create
+cluster: roadmap
+sub: create
 skills: [agent-docs-writing]
 description: Interactively create a new roadmap file in agents/roadmaps/
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "multi-phase work without an existing agents/roadmaps/*.md"
 ---
 
-# roadmap-create
-
+# /roadmap create
 ## Instructions
 
 ### 1. Determine location

package/.agent-src/commands/{roadmap-execute.md → roadmap/execute.md}

@@ -1,5 +1,7 @@
 ---
-name: roadmap-execute
+name: roadmap:execute
+cluster: roadmap
+sub: execute
 skills: [agent-docs-writing]
 description: Read and interactively execute a roadmap from agents/roadmaps/
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "existing agents/roadmaps/*.md referenced in the prompt"
 ---
 
-# roadmap-execute
-
+# /roadmap execute
 ## Instructions
 
 ### 1. Find the roadmap

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

@@ -0,0 +1,44 @@
+---
+name: roadmap
+description: Roadmap orchestrator — routes to create, execute
+cluster: roadmap
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "create a roadmap, execute a roadmap, plan a roadmap interactively"
+  trigger_context: "user wants to scaffold or run a roadmap under agents/roadmaps/"
+---
+
+# /roadmap
+
+Top-level orchestrator for the `/roadmap` family. Replaces 2 standalone
+commands with a single entry point + sub-command dispatch.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/roadmap create` | `commands/roadmap/create.md` | Interactively create a new roadmap in `agents/roadmaps/` |
+| `/roadmap execute` | `commands/roadmap/execute.md` | Read and interactively execute a roadmap |
+
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+
+## Dispatch
+
+1. Parse the user's argument: `/roadmap <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions` section
+   verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and ask:
+
+   > 1. create — scaffold a new roadmap interactively
+   > 2. execute — run an existing roadmap step by step
+
+## Rules
+
+- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
+  authorizes it.
+- **Do NOT chain sub-commands.** One `/roadmap <sub>` per turn.
+- If the user invokes `/roadmap` with no argument, **show the menu** — do
+  not guess which sub-command they meant.

package/.agent-src/commands/{tests-create.md → tests/create.md}

@@ -1,5 +1,7 @@
 ---
-name: tests-create
+name: tests:create
+cluster: tests
+sub: create
 skills: [pest-testing]
 description: Write meaningful tests for the changes in the current branch
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "code changes on the branch without matching test changes"
 ---
 
-# tests-create
-
+# /tests create
 ## Instructions
 
 ### 1. Detect the test framework