Skip to content

feat(vscode): bundle the full template library + manual publish job - #5

Merged
tickets-forge-dev merged 2 commits into
masterfrom
feat/vscode-template-library
Jun 29, 2026
Merged

tickets-forge-dev merged 2 commits into
masterfrom
feat/vscode-template-library

Conversation

@tickets-forge-dev

Copy link
Copy Markdown
Owner

What

Brings the LoopFlow VS Code extension (0.3.0 → 0.4.0) up to date with the current .loop feature set and the repo's template library.

1. Tutorial — what the extension gives you

docs/index.html: a plain "what you get" lead-in, and the completion bullet now names the latest vocabulary (use skills, remember in, flow, for each, done when the skill "…" approves / scores N or more).

2. New from template → the full best-practice library

  • New from template now offers the whole repo library: bugfix, feature, brownfield-feature, refactor, cicd-check, security, clean-architecture, test-coverage, review-diff, plus the multi-file flows greenfield-app and load-spec.
  • Multi-file flows copy their support files (discover/design/story-template + sprint.yaml/plan.md) alongside the entry loop.
  • Single source of truth: a build-time sync:templates step copies /templates into the package; the synced dir is gitignored. Drops the stale bmad/foreach bundles.
  • Grammar / completion / hover / lint were already current — left untouched.

3. Publishing

  • New manual Publish VS Code extension workflow (workflow_dispatch) — publishes the extension alone via the existing VSCE_PAT secret, decoupled from the tag-driven npm release (which would fail on duplicate lib versions).

Verification

  • npm run build -w loop-vscode → sync + tsc + bundle clean
  • npm test -w loop-vscode → 14/14 pass
  • npm run package → .vsix builds, all 17 template files bundled under templates/

Note: dashboard-in-extension was intentionally skipped (output panel already streams a live trace) — can follow up if wanted.

🤖 Generated with Claude Code

tickets-forge-dev and others added 2 commits June 29, 2026 08:46
… publish

- New from template now offers the whole repo template library (bugfix, feature,
  brownfield-feature, refactor, cicd-check, security, clean-architecture,
  test-coverage, review-diff, greenfield-app, load-spec), synced from /templates
  at build so there is one source of truth. Drops the stale bmad/foreach bundles.
- Multi-file flows copy their support files (discover/design/story-template +
  sprint.yaml/plan.md) alongside the entry loop.
- Tutorial: state what the extension gives the user; list the latest vocabulary
  (use skills, remember in, flow, for each, done when the skill … approves/scores).
- Add a manual workflow_dispatch "Publish VS Code extension" job, decoupled from
  the npm release so it never republishes the @loop-lang/* libs.
- Bump loop-vscode 0.3.0 → 0.4.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…er menu

Reduce discovery friction: the command was Command-Palette-only. Now contributed
to file/newFile and explorer/context (folders). A right-clicked folder is passed
through as the target so it drops the template there without the folder prompt.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tickets-forge-dev
tickets-forge-dev merged commit a6326ff into master Jun 29, 2026
2 checks passed
@tickets-forge-dev
tickets-forge-dev deleted the feat/vscode-template-library branch June 29, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant