Skip to content
Back to skills

180 Fn 16 Ugn2 4e70678d

ASecurity

Update the existing plan-sync agent to support a `DRY_RUN` mode where it reports proposed changes without actually editing files.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 31, 2026
documentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 31, 2026

npx -y skills add tools-only/X-Skills --skill 180-fn-16-ugn2_4e70678d --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 180 Fn 16 Ugn2 4e70678d?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 180 Fn 16 Ugn2 4e70678d
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-180-fn-16-ugn2-4e70678d/badge)](https://www.skillsdirectory.com/skills/tools-only-180-fn-16-ugn2-4e70678d)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# fn-16-ugn.2 Update plan-sync agent for dry-run support

## Overview

Update the existing plan-sync agent to support a `DRY_RUN` mode where it reports proposed changes without actually editing files.

## Context

- Agent file: `plugins/flow-next/agents/plan-sync.md`
- This agent is spawned by both:
  - `/flow-next:work` (auto-trigger in phases.md step 3e)
  - `/flow-next:sync` (new manual trigger from fn-16-ugn.1)

## Changes Required

### 1. Add DRY_RUN Input

In the "Input from prompt" section, add:
```markdown
- `DRY_RUN` - "true" or "false" (optional, defaults to false)
```

### 2. Modify Phase 5 (Update Affected Tasks)

Current behavior edits files unconditionally. Add dry-run handling:

```markdown
## Phase 5: Update Affected Tasks

**If DRY_RUN is "true":**
Report what would be changed without using Edit tool:

```
Would update:
- fn-1.3: Change `UserAuth.login()` → `authService.authenticate()`
- fn-1.5: Change return type `boolean` → `AuthResult`
```

Do NOT use Edit tool. Skip to Phase 6.

**If DRY_RUN is "false" or not set:**
For each affected downstream task, edit only the stale references:
[...existing edit logic...]
```

### 3. Modify Phase 6 (Return Summary)

Update the summary format to indicate dry-run mode:

```markdown
## Phase 6: Return Summary

**If DRY_RUN:**
```
Drift detected: yes
- fn-1.2 used `authService` singleton instead of `UserAuth` class

Would update (DRY RUN):
- fn-1.3: Change references from `UserAuth.login()` to `authService.authenticate()`
- fn-1.4: Update expected return type from `boolean` to `AuthResult`

No files modified.
```

**If not DRY_RUN:**
[...existing summary format...]
```

## Key Points

- Don't break existing auto-trigger behavior (DRY_RUN defaults to false)
- Dry-run should still do full analysis (phases 1-4)
- Only phase 5 (Edit) and phase 6 (summary) change behavior
- Keep the same detailed reporting in dry-run mode

## Acceptance

- [ ] `DRY_RUN=true` prevents Edit tool usage
- [ ] `DRY_RUN=true` reports proposed changes clearly
- [ ] `DRY_RUN=false` or missing works exactly as before (no regression)
- [ ] Summary clearly indicates dry-run mode when active

## Done summary
Added DRY_RUN parameter to plan-sync agent. Phase 5 skips Edit tool when dry-run, Phase 6 shows "Would update (DRY RUN)" format with "No files modified" footer.
## Evidence
- Commits: 05e024af578e2d4200923574083e74e56813876b
- Tests: smoke_test.sh
- PRs:
## References

- Agent file: `plugins/flow-next/agents/plan-sync.md`
- Epic spec: `.flow/specs/fn-16-ugn.md`

Files in this skill

  • README.md912 B
  • skill.md2.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.