Skip to content
Back to skills

Ls Wf Repository Localsetup Conversion

ASecurity

Use when converting an existing repo to the current LocalSetup framework with backup, blocker, install, and verification gates.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsshellbashgit

Security analysis

A100/100

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

Scanned November 7, 2026

npx -y skills add CruxExperts/LocalSetup --skill ls-wf-repository-localsetup-conversion --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ls Wf Repository Localsetup Conversion?

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

Security grade badge for Ls Wf Repository Localsetup Conversion
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruxexperts-ls-wf-repository-localsetup-conversion/badge)](https://www.skillsdirectory.com/skills/cruxexperts-ls-wf-repository-localsetup-conversion)

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
---
name: ls-wf-repository-localsetup-conversion
description: Use when converting an existing repo to the current LocalSetup framework with backup, blocker, install, and verification gates.
metadata:
  version: "1.0"
---

Use this workflow when onboarding a repository that may already contain old LocalSetup files, adapter paths, lockfiles, or framework source.

Every conversion starts with a report-only run. Use one shell session so the report and apply steps share the exact target and backup paths. Do not add `--yes` to this first command:

```bash
target_root="$(git rev-parse --show-toplevel 2>/dev/null || pwd -P)"
backup_dir="$target_root/.localsetup/backups/conversion-$(date -u +%Y%m%dT%H%M%SZ)"
localsetup convert --target-directory "$target_root" --backup-dir "$backup_dir" --tools codex --packs core
```

Record the report output and stop unless it provides all of this evidence:

- blockers are empty; unmanaged or ambiguous content is a blocker
- the reported LocalSetup source checkout and target repository root are the intended roots
- the report names the same timestamped `backup_dir` and its `conversion-report.json` path

Only after that evidence is explicit may you run the applying command with the unchanged variables:

```bash
localsetup convert --target-directory "$target_root" --backup-dir "$backup_dir" --tools codex --packs core --yes
```

After apply, confirm the recorded backup and report exist, then run the verification and doctor commands in `ls/docs/REPO_CONVERSION.md`. Follow that guide for source-vs-target behavior, blocker handling, and rollback evidence.

Files in this skill

  • SKILL.md1.6 KB
  • workflow.yaml2.1 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.