workflow-template-extractor

Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "workflow-template-extractor" with this command: npx skills add heyvhuang/ship-faster/heyvhuang-ship-faster-workflow-template-extractor

Workflow: Template Extractor (Real Project → Template)

Goal: Turn a real project into a shareable, runnable template in templates/ with minimal manual cleanup.

This is intended for “proven projects” you want to reuse as a baseline for future builds.

Input (pass paths only)

  • source_repo_root: Path to the real project
  • target_repo_root: Ship Faster repository root (where templates/ lives)
  • run_dir: runs/template-extractor/active/<run_id>/
  • extract_spec.md: What to keep/remove/generalize (brand, copy, assets, integrations, auth gates)

Output (persisted)

  • 03-plans/extract-plan.md
  • 05-final/extract-summary.md
  • templates/<NNN>-<slug>/ (runnable)

Workflow

0) Initialize

  1. Create run_dir.
  2. Decide <slug> and <NNN> (next available template number).
  3. Copy source_repo_roottemplates/<NNN>-<slug>/ (no build outputs, no caches).

1) De-secrets + de-brand

Must do:

  • Remove secret values from all files (.env*, config, hard-coded tokens).
  • Replace project IDs (Stripe price IDs, Supabase URLs/keys, webhook secrets) with env var keys.
  • Replace branding (names/domains/logos) with neutral placeholders unless the template is intentionally branded.

2) Normalize template entry docs

Required files:

  • README.md (5‑minute runnable)
  • .env.local.example (keys only)
  • metadata.json (name + description)

Recommended:

  • Ensure scripts exist for dev, build, start
  • If lint/typecheck/format are missing and the repo is TS-heavy, add minimal guardrails (avoid heavy governance)

3) Verification

Document in 05-final/extract-summary.md:

  • install works
  • dev starts
  • build succeeds (or clearly document why it can’t without credentials)

Constraints

  • Never commit secret values.
  • Extraction should be “copy + cleanup”, not a refactor project.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

workflow-ship-faster

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

workflow-creator

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

workflow-feature-shipper

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

workflow-execute-plans

No summary provided by upstream source.

Repository SourceNeeds Review