Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

releasing-skiller

Estrellas2

Forks0

Actualizado22 de junio de 2026, 03:34

Use when preparing, packaging, tagging, or publishing Skiller Desktop releases, including GitHub release CI, macOS code signing, notarization, release secrets, and desktop version bumps.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

gannonh

gannonh/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Explorador de archivos

3 archivos

SKILL.md

readonly

name	releasing-skiller
description	Use when preparing, packaging, tagging, or publishing Skiller Desktop releases, including GitHub release CI, macOS code signing, notarization, release secrets, and desktop version bumps.

Releasing Skiller

Use this for Skiller Desktop releases.

Release Target

Version source: apps/desktop/package.json
Tag format: desktop-vX.Y.Z
Workflow: .github/workflows/desktop-release.yml
Product name: Skiller
Bundle id: com.gannonhall.skiller

Workflow

Work from a clean tree. If already on a feature branch, use that branch for the release PR. If on main, create a release branch named release/desktop-vX.Y.Z before changing files.
Bump apps/desktop/package.json.
Write the changelog entry for the release.
Update README.md for user-facing install, usage, or release changes.
Run local checks:
- pnpm typecheck
- pnpm --filter @skiller/core test
- pnpm --filter @skiller/desktop test
- pnpm test:e2e
- pnpm --filter @skiller/desktop run desktop:dist:mac
- pnpm --dir apps/desktop exec electron-builder --config electron-builder.yml --linux AppImage deb --x64
Update AGENTS.md if the release introduces agent context worth preserving, such as major architecture changes or ADR-level decisions. Do not add obvious, standard, or one-off implementation details.
Open the release PR using references/release-pr-template.md.
Update the user on release PR status and wait for next steps. Do not merge without prior user approval.
On merge to main, CI creates desktop-vX.Y.Z and publishes macOS and Linux artifacts.

Changelog and Release Notes

Add a release entry before tagging.
Use the changelog entry as the GitHub Release notes content.
Include only user-facing changes, fixes, known issues, and install notes.
Keep internal implementation details out unless users need them.
Update README.md when the release changes installation, setup, commands, supported platforms, or visible behavior.

Read references/desktop-release.md before changing release CI or troubleshooting signing. Use references/release-pr-template.md when opening release PRs.

Más de este repositorio

mismo repositorio

mobile-e2e-test-author

gannonh/skills

Author local Maestro iOS-Simulator E2E flows for the Kata Code mobile app using the reusable TS orchestrator and Kata-specific flows. Use when adding or updating flows under mobile-e2e/.

2026-06-252

upstream-assess

gannonh/skills

Assess and selectively port changes from the upstream T3 Code fork (pingdotgg/t3code) into Kata Code. Use whenever the user wants to review what upstream has done, assess the diff, decide what to bring in, triage upstream commits, plan a vendor-pull, run an upstream scan, or figure out which upstream changes are worth porting. Covers scanning upstream since the last baseline, grouping commits by effort and risk, recommending Port/Skip/Watch per change, and re-implementing chosen changes as fork-original commits with Kata branding applied from the start.

2026-06-252

plan-build-verify

gannonh/skills

Use this skill for multi-step, spec-driven, or acceptance-gated implementation work that should move through Plan, Build, and Verify phases.

2026-06-242

kata-code-e2e-testing

gannonh/skills

Author local Playwright Electron E2E tests for Kata Code using the reusable harness and Kata-specific flows. Use when adding or updating tests under e2e/.

2026-06-222

handoff

gannonh/skills

Compact the current conversation into a handoff document for another agent to pick up.

2026-06-212

validate-kata-code-nightly-release

gannonh/skills

Validate Kata Code nightly releases on macOS with the @Computer plugin. Start and update the nightly app, use its New Project flow to create a timestamp-suffixed nightly UAT project under `/Volumes/EVO/dev`, then execute explicit acceptance criteria for a Codex GPT-5.4-Mini chat, Browser and Files panels, and git commit flow; capture criterion-level screenshots and write an evidence-linked report in the created project. Use when validating or documenting the Kata Code nightly release flow.

2026-06-202

Releasing Skiller

Use this for Skiller Desktop releases.

Release Target

Version source: apps/desktop/package.json

Tag format: desktop-vX.Y.Z

Workflow: .github/workflows/desktop-release.yml

Product name: Skiller

Bundle id: com.gannonhall.skiller

Workflow

Work from a clean tree. If already on a feature branch, use that branch for the release PR. If on main, create a release branch named release/desktop-vX.Y.Z before changing files.

Bump apps/desktop/package.json.

Write the changelog entry for the release.

Update README.md for user-facing install, usage, or release changes.

Run local checks:

pnpm typecheck
pnpm --filter @skiller/core test
pnpm --filter @skiller/desktop test
pnpm test:e2e
pnpm --filter @skiller/desktop run desktop:dist:mac
pnpm --dir apps/desktop exec electron-builder --config electron-builder.yml --linux AppImage deb --x64

Update AGENTS.md if the release introduces agent context worth preserving, such as major architecture changes or ADR-level decisions. Do not add obvious, standard, or one-off implementation details.

Open the release PR using references/release-pr-template.md.

Update the user on release PR status and wait for next steps. Do not merge without prior user approval.

On merge to main, CI creates desktop-vX.Y.Z and publishes macOS and Linux artifacts.

Changelog and Release Notes

Add a release entry before tagging.

Use the changelog entry as the GitHub Release notes content.

Include only user-facing changes, fixes, known issues, and install notes.

Keep internal implementation details out unless users need them.

Update README.md when the release changes installation, setup, commands, supported platforms, or visible behavior.

Read references/desktop-release.md before changing release CI or troubleshooting signing. Use references/release-pr-template.md when opening release PRs.