Skip to content
Back to skills

1247 Fn 17 Wti2 1ca8690f

ASecurity

Add a review backend question to the `/flow-next:setup` workflow.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 1, 2026
toolsbashbackend

Works with

  • cli

Security analysis

A100/100

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

Scanned June 1, 2026

npx -y skills add tools-only/X-Skills --skill 1247-fn-17-wti2_1ca8690f --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 1247 Fn 17 Wti2 1ca8690f?

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

Security grade badge for 1247 Fn 17 Wti2 1ca8690f
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-1247-fn-17-wti2-1ca8690f/badge)](https://www.skillsdirectory.com/skills/tools-only-1247-fn-17-wti2-1ca8690f)

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-17-wti.2 Add review backend question to /flow-next:setup

## Description
Add a review backend question to the `/flow-next:setup` workflow.

## File to modify

`plugins/flow-next/skills/flow-next-setup/workflow.md`

## Changes

### Step 6: Add detection before questions

Before the `AskUserQuestion` block, add tool detection:

```bash
# Detect available review backends
HAVE_RP=$(which rp-cli >/dev/null 2>&1 && echo 1 || echo 0)
HAVE_CODEX=$(which codex >/dev/null 2>&1 && echo 1 || echo 0)

# Read current config value if exists
CURRENT_BACKEND=$("${PLUGIN_ROOT}/scripts/flowctl" config get review.backend --json 2>/dev/null | jq -r '.value // empty')
```

### Step 6: Add question to AskUserQuestion block

Add a new question to the existing `questions` array (after Plan-Sync, before Docs):

```json
{
  "header": "Review",
  "question": "Which review backend for Carmack-level reviews?",
  "options": [
    {"label": "Codex CLI (Recommended)", "description": "Cross-platform, uses GPT 5.2 High. Detected: <yes/no>"},
    {"label": "RepoPrompt", "description": "macOS only, visual context builder. Detected: <yes/no>"},
    {"label": "None", "description": "Skip reviews, can configure later with --review flag"}
  ],
  "multiSelect": false
}
```

**Dynamic options based on detection:**
- If `HAVE_CODEX=0`: Change Codex description to include "(not detected)"
- If `HAVE_RP=0`: Change RepoPrompt description to include "(not detected)"
- If neither detected: Add note "Neither rp-cli nor codex detected. Install one for review support."

**Pre-selection for re-runs:**
- If `CURRENT_BACKEND` is set, note it in the question: "Current: <backend>"

### Step 7: Process answer

Add handling for Review answer:

```bash
# Review backend
case "$review_answer" in
  "Codex"*) REVIEW_BACKEND="codex" ;;
  "RepoPrompt"*) REVIEW_BACKEND="rp" ;;
  *) REVIEW_BACKEND="none" ;;
esac

"${PLUGIN_ROOT}/scripts/flowctl" config set review.backend "$REVIEW_BACKEND" --json
```

### Step 8: Update summary

Add to the Configuration section:

```
Configuration:
- Memory: <enabled|disabled>
- Plan-Sync: <enabled|disabled>
- Review backend: <codex|rp|none>
```
## Acceptance
- [ ] Setup workflow detects rp-cli and codex availability
- [ ] Review backend question added to AskUserQuestion block
- [ ] Question shows detection status (detected/not detected)
- [ ] Re-run setup shows current config value
- [ ] Answer is written to config via `flowctl config set review.backend`
- [ ] Summary shows configured review backend
- [ ] Works when neither tool detected (defaults to "none")
## Done summary
Added review backend question to /flow-next:setup workflow with detection for rp-cli and codex, answer mapping to config, and summary output. Includes jq dependency note.
## Evidence
- Commits: 97f49822c8b4b4f8dc7d3f0baec4b9e6cd58eb0e, f2cb6f59e0c9cd1b1c5cf7fe152946837321d8f2
- Tests: Manual inspection of workflow.md
- PRs:

Files in this skill

  • README.md823 B
  • skill.md2.8 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.