Agent skill

Nightly Changelog

by LunCoSim in LunCoSim/lunco-sim

Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link.

Apache-2.0Auto-check passedDevelopment

Install Nightly Changelog

skills CLI
$ npx skills add LunCoSim/lunco-sim --skill nightly-changelog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LunCoSim/lunco-sim nightly-changelog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LunCoSim/lunco-sim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nightly-changelog .claude/skills/nightly-changelog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nightly-changelog
GitHub stars
107
Token cost
~1.1k tokens
SKILL.md length
495 words
Files
3 (incl. scripts)
Skills in repo
40
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link.

  • Works in 6 steps: Inspect repository state without… → Establish the range. By default, use the… → Generate the Markdown with the bundled… → …
  • Preparing a nightly build
  • SKILL.md covers Workflow and Output Contract
  • Runs Python scripts from its folder; calls git, python3 and gh

What it does

Nightly Changelog is an agent skill from LunCoSim/lunco-sim. Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link. Use when preparing a nightly build, updating docs/releases Markdown, or wiring release notes into .github/workflows/nightly.yml. Preserve dirty worktrees and do not edit Rust source.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/generate_changelog.py` and `tests/test_generate_changelog.py`).

It sits in Development, covering Changelog and release notes. It works with GitHub, GitHub Actions and Rust. The repository describes itself as: Collaborative Multiphysics Cosimulator For Space Missions 🌎🚀🌚. The licence is Apache-2.0.

When your agent uses it

  • Preparing a nightly build
  • Updating docs/releases Markdown
  • Wiring release notes into .github/workflows/nightly.yml

Example prompts

  • “/nightly-changelog”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Inspect repository state without changing it
  2. Establish the range. By default, use the newest tag matching nightly-YYYYMMDDTHHMMSSZ as the base and HEAD as the target. For a rerun…
  3. Generate the Markdown with the bundled script
  4. Review the standalone changelog for the complete previous-nightly change range. Review release notes separately for correct installer…
  5. Add or update the release workflow only in .github/workflows/nightly.yml. The release job must fetch timestamped tags, generate the GitHub…
  6. Validate without Rust edits

What it can do on your machine

Read from SKILL.md and the folder at commit 4c48dd0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • python3
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nightly Changelog loads about 1.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 495 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LunCoSim/lunco-sim at commit 4c48dd0, republished under its Apache-2.0 licence (© LunCoSim). 495 words, ~1,084 tokens.

Download SKILL.mdSave it as .claude/skills/nightly-changelog/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
nightly-changelog
description
Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link. Use when preparing a nightly build, updating docs/releases Markdown, or wiring release notes into .github/workflows/nightly.yml. Preserve dirty worktrees and do not edit Rust source.

Nightly Changelog

Create short, human-facing notes for the exact commit being built. Keep the committed Markdown snapshot in docs/releases/ and use the generator in this skill for future GitHub Release bodies.

Workflow

  1. Inspect repository state without changing it:

    bash
    git status --short --branch
    git tag --list 'nightly-*'
    git log -1 --format='%H %cI %s' HEAD

    Preserve unrelated dirty files. The changelist describes committed changes in the release range; report uncommitted work separately and never silently include it.

  2. Establish the range. By default, use the newest tag matching nightly-YYYYMMDDTHHMMSSZ as the base and HEAD as the target. For a rerun, pass explicit refs. Do not use the legacy rolling nightly tag as the baseline.

  3. Generate the Markdown with the bundled script:

    bash
    python3 skills/nightly-changelog/scripts/generate_changelog.py \
      --from-ref latest \
      --to-ref HEAD \
      --release-date 2026-08-02 \
      --output docs/releases/nightly-20260802.md

    The default format emits the standalone changelog with all non-merge changes since the previous nightly. The release-notes format emits only platform download/install instructions, a brief autoupdater availability note, a prompt for an AI agent to use the installed documentation, skills, and examples to build a mission, and a changelog link. It does not inspect or modify source files.

  4. Review the standalone changelog for the complete previous-nightly change range. Review release notes separately for correct installer names, concise wording, the brief autoupdater note, and a working changelog link. Do not add updater mechanics or claim runtime validation to the GitHub release body.

  5. Add or update the release workflow only in .github/workflows/nightly.yml. The release job must fetch timestamped tags, generate the GitHub body with --format release-notes from the exact github.sha, and publish those notes with the artifacts. Keep the detailed changelog output in its separate docs/releases/ snapshot; never pass that output as the GitHub release body. A local Markdown file is GitHub-visible only after the containing commit is pushed; a release body is the immediate GitHub-facing copy.

    The metadata job must produce one validated release_tag together with the shared UTC timestamp, and the release job must propagate that output explicitly. Fail before any gh release create call if the value is empty or begins with untagged-; GitHub's generated untagged draft is not a valid nightly release and cannot receive the Velopack upload contract.

  6. Validate without Rust edits:

    bash
    python3 skills/nightly-changelog/scripts/generate_changelog.py --help
    quick_validate.py skills/nightly-changelog
    git diff --check
    git status --short

    Run the repository's normal CI or packaging checks only when requested. Do not claim that a nightly build, upload, tag, or release exists until its GitHub Actions result is observed.

Show full SKILL.md (121 more words)Show less

Output Contract

  • Store committed snapshots at docs/releases/nightly-YYYYMMDD.md.
  • Generate changelog snapshots with the default format; generate GitHub release bodies with --format release-notes.
  • Include exactly the four supported human installer names.
  • Mention that the built-in autoupdater can download the latest nightly build.
  • Include the short mission-building prompt for the user's favorite AI agent.
  • Include all non-merge changes since the previous timestamped nightly in the standalone changelog.
  • Link the exact source range from the release body without copying its changes into that body.
  • Keep updater feeds, updater mechanics, verification claims, and worktree details out of the human-facing release body.

The generator is intentionally dependency-free beyond Python 3 and Git. Keep the logic deterministic so a rerun over the same refs produces the same changelist.

© LunCoSim, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/nightly-changelog of LunCoSim/lunco-sim.

  • SKILL.md
  • scripts/generate_changelog.py
  • tests/test_generate_changelog.py

Open the folder on GitHubat commit 4c48dd0

Compare with similar skills

Nightly Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nightly Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nightly Changelog this skillLunCoSim/lunco-sim107—~1.1kAutomated safety check: PassApache-2.0
Worktrunk Release Workflowmax-sixty/worktrunk9.2k—~7.5kAutomated safety check: PassCustom licence
Ccb GitHubSeemSeam/claude_codex_bridge3.6k—~4.9kAutomated safety check: PassCustom licence
Cut Releasedelexw/claude-code-trace3761 repos~1.4kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
Cline CLI Release Publishercline/cline70k—~3.4kAutomated safety check: WarnApache-2.0

Similar skills

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9.2k GitHub stars~7.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Ccb GitHub

    SeemSeam/claude_codex_bridge

    Maintain this CCB project's GitHub-facing release and npm publication surface.

    3.6k GitHub stars~4.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Cut Release

    delexw/claude-code-trace

    Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.

    376 GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.

    70k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check: warnings
  • Create Release Checklist

    software-mansion/smelter

    Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.

    734 GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check: notes

More from LunCoSim/lunco-sim

All 40 skills in this repo
  • Build or repair a reusable scene component through a live LunCoSim Editor session.

    107 GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Assembly Quality

    LunCoSim/lunco-sim

    Build or review a componentized LunCoSim USD assembly with a realistic, dimensionally checkable presentation.

    107 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Author Rhai Tests

    LunCoSim/lunco-sim

    Author and review LunCoSim behavioral, asset-backed, component, mission, visual, and requirements-verification tests.

    107 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Author Rhai Tool

    LunCoSim/lunco-sim

    Create, extend, register, or debug a reusable LunCoSim Rhai tool library for live USD authoring, component linting, inspection, or test support.

    107 GitHub stars~5.2k tokensUpdated today
    Auto-check passed
  • Author Tutorial

    LunCoSim/lunco-sim

    Author an interactive tutorial, guided lesson, onboarding flow, coach-mark tour, or objectives checklist in LunCoSim.

    107 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Capability Discovery

    LunCoSim/lunco-sim

    Find existing LunCoSim capabilities before declaring a feature missing, unsupported, or impossible.

    107 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Nightly Changelog

What does Nightly Changelog do?

Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link. Nightly Changelog is an agent skill from LunCoSim/lunco-sim. Generate concise LunCoSim nightly GitHub release notes with platform downloads, installation guidance, an AI-agent mission prompt, and a changelog link.

When should I use Nightly Changelog?

Nightly Changelog fits situations like: preparing a nightly build; updating docs/releases Markdown; wiring release notes into .github/workflows/nightly.yml.

How do I install Nightly Changelog in Claude Code?

Run `npx skills add LunCoSim/lunco-sim --skill nightly-changelog -a claude-code`. Or copy the skill folder (skills/nightly-changelog in LunCoSim/lunco-sim) into .claude/skills/nightly-changelog in your project. Claude Code loads it when a task matches its description.

How do I install Nightly Changelog in Codex?

Run `npx skills add LunCoSim/lunco-sim --skill nightly-changelog -a codex`. Or copy the skill folder (skills/nightly-changelog in LunCoSim/lunco-sim) into .agents/skills/nightly-changelog in your project. Codex loads it when a task matches its description.

Can I use Nightly Changelog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LunCoSim/lunco-sim --skill nightly-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nightly-changelog, .gemini/skills/nightly-changelog, .github/skills/nightly-changelog and .opencode/skills/nightly-changelog in your project.

What does Nightly Changelog need to run?

Going by SKILL.md and its folder, Nightly Changelog needs Python for the scripts in its folder and the command-line tools its instructions call (git, python3 and gh). Our summary lists: Python 3.

Does Nightly Changelog access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nightly Changelog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nightly Changelog use?

Nightly Changelog is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nightly Changelog use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nightly Changelog?

Skills that share tags, products or a category with Nightly Changelog: Worktrunk Release Workflow (max-sixty/worktrunk, 9.2k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Cut Release (delexw/claude-code-trace, 376 stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nightly Changelog?

LunCoSim (a GitHub organization) maintains it in LunCoSim/lunco-sim, which has 107 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 11, 2026.

Source: LunCoSim/lunco-sim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.