Run any Skill in Manus with one click

build-local

Stars3

Forks1

UpdatedMarch 31, 2026 at 04:40

Build axiforge locally for beta testing. Use when asked to run the repo's local beta packaging flow, including validation tests, beta version stamping, artifact builds, release creation, and Discord notification.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

darkharasho

darkharasho/axiforge

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	build-local
description	Build axiforge locally for beta testing. Use when asked to run the repo's local beta packaging flow, including validation tests, beta version stamping, artifact builds, release creation, and Discord notification.

Build Local

This skill imports the existing repo workflow from .claude/commands/build-local.md.

Use it when the user wants a local beta build for this repository.

Workflow

Run npm test. If tests fail, stop and report that the build is blocked.
Stamp a temporary beta version into package.json. Format: <base>-beta.YYYYMMDDTHHMM. Do not commit this change.
Clean build output directories:

dist/
dist_out/

Build artifacts in order:

npm run build:site
npm run build:renderer
npx electron-builder --linux --win --publish never

If Windows packaging fails because Wine is unavailable, retry with Linux-only packaging and report that limitation.
Restore package.json after the build so the beta stamp does not remain in the working tree.
Create the GitHub release using the built version from artifact filenames. Generate patch notes from commits since the last tag or initial commit if needed.
Read DISCORD_WEBHOOK_URL from .env and post the release summary to Discord. If the webhook is missing, warn and continue.
End by listing built artifact paths, the release URL, and whether Discord was notified.

More from this repository

same repository

fix-issue

darkharasho/axiforge

Fix a GitHub bug issue for the axiforge Electron app. Use when asked to resolve issue-driven bugs in this repo with labels, project tracking, repro tests, branch/PR flow, and manual verification.

2026-04-203

add-feature

darkharasho/axiforge

Implement a GitHub enhancement issue for the axiforge Electron app. Use when asked to work issue-driven feature requests in this repo, including triage labels, project status updates, branch/PR flow, tests, and manual verification.

2026-03-313

release

darkharasho/axiforge

Run the axiforge release workflow. Use when asked to produce either a beta or official release for this repo, including validation, versioning, packaging, GitHub release steps, and optional extended test suites.

2026-03-313

triage-issue

darkharasho/axiforge

Triage a GitHub issue in the axiforge repo. Use when asked to classify an issue as bug, enhancement, or question before deeper work.

2026-03-313

name	build-local
description	Build axiforge locally for beta testing. Use when asked to run the repo's local beta packaging flow, including validation tests, beta version stamping, artifact builds, release creation, and Discord notification.

Build Local

This skill imports the existing repo workflow from .claude/commands/build-local.md.

Use it when the user wants a local beta build for this repository.

Workflow

Run npm test. If tests fail, stop and report that the build is blocked.
Stamp a temporary beta version into package.json. Format: <base>-beta.YYYYMMDDTHHMM. Do not commit this change.
Clean build output directories:

dist/
dist_out/

Build artifacts in order:

npm run build:site
npm run build:renderer
npx electron-builder --linux --win --publish never

If Windows packaging fails because Wine is unavailable, retry with Linux-only packaging and report that limitation.
Restore package.json after the build so the beta stamp does not remain in the working tree.
Create the GitHub release using the built version from artifact filenames. Generate patch notes from commits since the last tag or initial commit if needed.
Read DISCORD_WEBHOOK_URL from .env and post the release summary to Discord. If the webhook is missing, warn and continue.
End by listing built artifact paths, the release URL, and whether Discord was notified.