zoom-out · diff
v1.1.0 to v1.1.1
2 added, 2 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: zoom-out
- version: 1.1.0
+ version: 1.1.1
description: "User-invoked only, via /zoom-out — never auto-fires. Steps back from the current code to give a higher-level perspective: which modules are involved, how do they connect, what is this change touching that isn't obvious? Reads the project's CONTEXT.md / domain glossary when available. Invoke it deliberately when you feel stuck in detail, when a change feels bigger than expected, or before making a structural decision and you want a map first."
disable-model-invocation: true
requires_agent_teams: false
- requires_claude_code: true
+ requires_claude_code: false
min_plan: starter
owns:
directories: []
patterns: []
shared_read: ["*"]
allowed-tools: ["Read", "Grep", "Glob"]
composes_with: ["maintain-context"]
spawned_by: []
---
# zoom-out
Go up a layer. Map the modules involved in this change. Read the domain glossary (`CONTEXT.md`, configured via `setup-project-skills`) if one exists.
Output a numbered list of modules, one line per module describing its role, with arrows (`→`) showing connections between them. Example shape:
```text
1. AuthService — validates JWTs → 2. UserRepo
2. UserRepo — loads/persists users → 3. SessionStore
3. SessionStore — refresh-token cache → AuthService
```
Do not propose changes. The user asked for orientation, not a fix — if they wanted a fix they'd have invoked a different skill.