dejavu

Automate version bumps, builds, packaging, and GitHub releases for MatrixShader.

2|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/matrixshader/matrix-shader --skill dejavu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dejavu
Source: https://github.com/matrixshader/matrix-shader/tree/main/.claude/skills/dejavu
Command: npx skills add https://github.com/matrixshader/matrix-shader --skill dejavu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a multi-component release across C# projects, installer, website, and GitHub is manual, error-prone, and slow; this Skill automates the entire release workflow so versions, builds, artifacts, and deployments stay in sync.

Core Features & Use Cases

  • Atomic version bump across all required files (Directory.Build.props, installers, website, and package.json) with validation that all expected patterns exist.
  • Rebuild and package all C# executables, collect publish outputs, create a ZIP archive, and optionally build an Inno Setup installer.
  • Release publishing: commit and push version bumps, create a GitHub release with ZIP and installer assets, generate a changelog from recent commits, and verify website deployment.
  • Use case: A maintainer needs to cut a patch, minor, or major release and wants a reproducible, verifiable process that updates files, builds binaries, packages artifacts, and publishes a GitHub release with minimal manual steps.

Quick Start

Invoke the dejavu skill with the desired level or semver, for example /dejavu patch, to run the full coordinated release process.

Frequently Asked Questions about dejavu

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps and builds for a C# project and GitHub release?

Automating version bumps and builds for a C# project involves updating Directory.Build.props and installers, then rebuilding binaries to generate GitHub release assets. This Skill automates that workflow, validating patterns and packaging outputs.

What is the best way to coordinate a multi-component release across a C# installer and website?

Coordinating a multi-component release requires synchronizing version numbers, binaries, and website deployments atomically. This Skill orchestrates the process by bumping versions across required files, packaging installers, and verifying website deployment.

Do I need Inno Setup and the gh CLI to automate C# release deployments?

Yes, you need the gh CLI to create GitHub releases and Inno Setup to build the installer. The Skill requires both tools for full deployment automation, although you can explicitly skip Inno Setup if unavailable.

Can I generate a changelog from recent commits when publishing a GitHub release?

Generating a changelog from recent commits during GitHub release publishing is supported. The Skill commits and pushes version bumps, creates the release with ZIP and installer assets, and generates a changelog from recent commit history.

How do I run a patch release using PowerShell publish scripts for C# executables?

Running a patch release with PowerShell publish scripts requires invoking the automation with the desired level, such as specifying patch. The Skill then rebuilds all C# executables, collects publish outputs, and creates a ZIP archive.