Javdb Cli Release Notes logo

Javdb Cli Release Notes

Community
FlanChanXwO
javdb-cli-release-notes

Prepare javdb-cli bilingual versioned changelogs with verified source attribution, coordinate an authorized release, recover downstream publishers, or synchronize historical Release bodies. Use for release work, not ordinary PR release metadata.

Overview

PublisherFlanChanXwO
Repositoryjavdb-cli
Skill namejavdb-cli-release-notes
Stars
76
Forks
15
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by FlanChanXwO on GitHub. Read the source before you install it.

Installation

Install the Javdb Cli Release Notes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-release-notes
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/FlanChanXwO/javdb-cli.git /tmp/javdb-cli
mkdir -p .claude/skills
cp -r /tmp/javdb-cli/.agents/skills/javdb-cli-release-notes .claude/skills/javdb-cli-release-notes
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Javdb Cli Release Notes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Javdb Cli Release Notes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Javdb Cli Release Notes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Prepare a javdb-cli Release

Read AGENTS.md, docs/maintainers/development.md, and current release/publisher workflows. Resolve the exact version, prior tag, target commit, and authorized actions. Choosing a version does not itself permit a release-prep PR, merge, tag, publication, or history rewrite.

Prepare and audit

  1. Resolve the prior release with sh scripts/previous-release-tag.sh vX.Y.Z, using the approved target version.
  2. Use go run ./scripts/releasenotes audit for the exact range and keep its report in a temporary location. Inspect current help for arguments. Squash attribution only accepts a verified PR whose merge_commit_sha equals the commit; a title suffix alone is not evidence.
  3. Edit changelog/vX.Y.Z/en.md and zh-CN.md and their navigation. Entries carry real PR/direct-commit sources and both locales have the same source set. JavDB validates that referenced sources belong to the range; unlike Pixiv, its current policy does not require every in-range source to appear in notes.
  4. If skills/javdb-cli/ changed since the previous release, update its sole version to the approved SemVer and synchronize the README's published-skill version. If unchanged, preserve its prior version and verify the publisher's unchanged-skill branch. Do not bump it mechanically for every CLI release or publish maintenance skills as the product.
  5. Run sh scripts/test-releasenotes.sh and the release-note tool's validate command with the version, previous tag, directory, and matching audit. Re-run audit and validate --audit on the exact final merged commit before creating a tag. Missing attribution, malformed notes, or API failures block tagging.

Ordinary feature PRs do not fill release-note metadata or edit versioned notes. changelog/unreleased/ is an optional manual draft area, not an automatic workflow input.

Publication and recovery

JavDB's release workflow accepts tag pushes and an authorized release_tag dispatch, both subject to source verification. Tests, production archives, verified containers and the immutable handoff precede the single release-approval gate. Signing and publication consume the approved identity; do not retag, rebuild different bytes under it, or bypass approval.

Homebrew, ClawHub and the container publisher run independently from a successful Release handoff. Manual recovery takes the original release_run_id; publish-dockerhub.yml publishes both GHCR and Docker Hub. Follow current workflow inputs and artifact hashes instead of treating the latest main commit as the release source. Check channel outcomes separately and preserve stable/prerelease promotion rules.

Historical bodies

Use validate, audit, render, and sync-history through the existing tool. Dry-run each explicitly selected historical version first; only an approved --apply may change the remote Release body. Never create tags or replace assets as part of body synchronization. Read the result back and compare with local bilingual rendering.

Report the version, source range, Release run, actual evidence, publisher state, and remaining blockers. Do not log GitHub tokens, signing keys, account credentials, or private data. A submitted skill awaiting review is not a publicly accepted publication.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Javdb Cli Release Notes AI skill do?

Prepare javdb-cli bilingual versioned changelogs with verified source attribution, coordinate an authorized release, recover downstream publishers, or synchronize historical Release bodies. Use for release work, not ordinary PR release metadata.

Why use Javdb Cli Release Notes on TypingMind?

Because you install it once and use it with any model. Javdb Cli Release Notes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Javdb Cli Release Notes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-release-notes. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Javdb Cli Release Notes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Javdb Cli Release Notes?

As many as you like. As long as a model supports skills, you can use Javdb Cli Release Notes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Javdb Cli Release Notes AI skill free?

Yes. It is published on GitHub by FlanChanXwO under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇