New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Deploy Process

by trkbt10 in trkbt10/indexion

Release process for indexion. An agent skill from trkbt10/indexion.

Apache-2.0Auto-check passedDevOps & Cloud

Install Deploy Process

skills CLI
$ npx skills add trkbt10/indexion --skill deploy-process -a claude-code

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

GitHub CLI
$ gh skill install trkbt10/indexion deploy-process --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/trkbt10/indexion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deploy-process .claude/skills/deploy-process && 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
deploy-process
GitHub stars
153
Token cost
~1.4k tokens
SKILL.md length
430 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Release process for indexion. An agent skill from trkbt10/indexion.

  • Works in 9 steps: Commit feature changes → Update RELEASE_NOTES.md → Run local verification → …
  • The user asks to release
  • SKILL.md covers Prerequisites, Version Convention, Release Steps and Push Safety, plus 3 more sections
  • Calls git, bun and bash

What it does

Deploy Process is an agent skill from trkbt10/indexion. Release process for indexion. Use when the user asks to release, deploy, bump version, create a tag, or push a release. Ensures submodule→parent push ordering, version sync, and tag consistency.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: source code exploration and documentation tool. The licence is Apache-2.0.

When your agent uses it

  • The user asks to release
  • Tasks that involve Deployment

Example prompts

  • “/deploy-process”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Commit feature changes
  2. Update RELEASE_NOTES.md
  3. Run local verification
  4. Bump version in moon.mod
  5. Run sync-version.sh
  6. Commit version in skills submodule
  7. Create release commit (WITHOUT tag)
  8. Push and wait for CI
  9. Create and push tag (after CI passes)

What it can do on your machine

Read from SKILL.md and the folder at commit 9a074ca. 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

    Shell commands in SKILL.md call:

    • git
    • bun
    • bash

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Deploy Process loads about 1.4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 430 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from trkbt10/indexion at commit 9a074ca, republished under its Apache-2.0 licence (© trkbt10). 430 words, ~1,396 tokens.

Download SKILL.mdSave it as .claude/skills/deploy-process/SKILL.md (or your agent's skills folder).
name
deploy-process
description
Release process for indexion. Use when the user asks to release, deploy, bump version, create a tag, or push a release. Ensures submodule→parent push ordering, version sync, and tag consistency.

indexion Release Process

Prerequisites

  • .gitmodules has pushRecurseSubmodules = on-demand for all submodules
  • scripts/sync-version.sh exists and syncs moon.mod → version.mbt + marketplace.json + plugin.json

Version Convention

  • SoT: moon.mod → version field (TOML)
  • Semver: MAJOR.MINOR.PATCH
  • Tags: v{VERSION} (e.g. v0.8.0)
  • Propagation targets:
    • src/update/version.mbt → current_version constant
    • skills/.claude-plugin/marketplace.json → "version" field
    • skills/.claude-plugin/plugin.json → "version" field

Release Steps

1. Commit feature changes

Commit all feature/fix changes BEFORE the version bump. The release commit should contain ONLY version changes.

If submodules have changes:

bash
# kgfs submodule
cd kgfs && git add -A && git commit -m "feat: ..." && cd ..

# skills submodule
cd skills && git add -A && git commit -m "feat: ..." && cd ..

# Parent: stage submodule refs + changed files
git add kgfs skills src/ cmd/ ... && git commit -m "feat: ..."
2. Update RELEASE_NOTES.md

Prepend release notes for the new version at the top of RELEASE_NOTES.md:

markdown
# vX.Y.Z

## Highlights

- **Feature A** — Brief description
- **Feature B** — Brief description

## New Features

### Feature A

Detailed description...

## Improvements

- Item 1
- Item 2

## Bug Fixes

- Fix 1
- Fix 2

---

# vX.Y-1.Z (previous version header follows)

Use git log vPREV..HEAD --oneline to review commits since last release.

3. Run local verification

Before bumping version, verify all checks pass locally:

bash
# MoonBit tests
moon test --target native

# TypeScript tests
bun run test

# Lint
bun run lint
4. Bump version in moon.mod

Edit moon.mod and change the version field (TOML: version = "x.y.z"):

  • +0.0.1 for patches (bug fixes)
  • +0.1.0 for minor (new features, backward compatible)
  • +1.0.0 for major (breaking changes)
5. Run sync-version.sh
bash
bash scripts/sync-version.sh

This propagates the version to version.mbt and marketplace.json.

6. Commit version in skills submodule

marketplace.json lives inside the skills submodule, so it needs its own commit:

bash
cd skills && git add .claude-plugin/marketplace.json .claude-plugin/plugin.json && git commit -m "release: vX.Y.Z" && cd ..
7. Create release commit (WITHOUT tag)
bash
git add moon.mod src/update/version.mbt skills RELEASE_NOTES.md
git commit -m "release: vX.Y.Z"

DO NOT create the tag yet.

8. Push and wait for CI
bash
git push

push.recurseSubmodules = on-demand ensures:

  1. kgfs submodule is pushed first
  2. skills submodule is pushed second
  3. Parent is pushed last

Then verify that every submodule commit actually reached its remote — on-demand has been observed to push only one of the two submodules, and CI then fails at checkout with "Fetched in submodule path 'kgfs', but it did not contain ...":

bash
git -C kgfs fetch -q origin && git -C kgfs log origin/main..HEAD --oneline   # must be empty
git -C skills fetch -q origin && git -C skills log origin/main..HEAD --oneline # must be empty
# if not empty: git -C kgfs push origin main   (resp. skills)

A failed run cannot be re-run without admin rights on the repository, so a missed submodule push costs an extra commit on main to retrigger CI. Check before pushing the parent, not after.

Wait for CI to pass on GitHub Actions. Check the workflow status before proceeding.

Show full SKILL.md (138 more words)Show less
9. Create and push tag (after CI passes)

Only after CI passes:

bash
git tag -a vX.Y.Z -m "release: vX.Y.Z"
git push origin vX.Y.Z

Use git tag -a (annotated tag) for proper release semantics.

Push Safety

The .gitmodules file enforces pushRecurseSubmodules = on-demand for all submodules. This is a repository-level setting that applies to every clone.

Additionally, .git/config has the same setting as a local override. Both are needed:

  • .gitmodules: shared across clones (checked into git)
  • .git/config: applies immediately to the current working copy

Verification

After push, verify:

bash
# Tags are consistent
git tag --sort=-v:refname | head -1  # should be vX.Y.Z

# Submodules point to pushed commits
git submodule status  # no + prefix = clean

# Version is consistent across all targets
grep '^version' moon.mod
grep 'current_version' src/update/version.mbt
grep '"version"' skills/.claude-plugin/marketplace.json
grep '"version"' skills/.claude-plugin/plugin.json

Rollback

If CI fails after pushing the release commit:

bash
# Fix the issue locally
# Commit the fix
git add ... && git commit -m "fix: ..."

# Push the fix
git push

# Wait for CI to pass, then proceed to step 9

If the tag was already pushed and needs to be removed:

bash
# Remove tag from remote
git push origin :refs/tags/vX.Y.Z

# Remove tag locally
git tag -d vX.Y.Z

# After fixing issues, recreate the tag on the correct commit
git tag -a vX.Y.Z -m "release: vX.Y.Z"
git push origin vX.Y.Z

DO NOT

  • Do NOT create the tag before CI passes
  • Do NOT amend the release commit after pushing
  • Do NOT force-push to main
  • Do NOT skip sync-version.sh — manual version editing causes drift
  • Do NOT push parent before submodules — on-demand handles this, don't override

© trkbt10, 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

Just SKILL.md in .claude/skills/deploy-process of trkbt10/indexion.

Open the folder on GitHubat commit 9a074ca

Compare with similar skills

Deploy Process 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.

Deploy Process compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deploy Process this skilltrkbt10/indexion153—~1.4kAutomated safety check: PassApache-2.0
Aspiremicrosoft/aspire.dev1964 repos~1.1kAutomated safety check: PassMIT
Releasebmeares/Meerschaum154—~1.1kAutomated safety check: NotesApache-2.0
Google Agents CLI Scaffoldpifferologo/cloud-agents-cli1291 repos~2.9kAutomated safety check: NotesApache-2.0
Agr Releasecomputerlovetech/agr451—~1.6kAutomated safety check: PassMIT
Cutting Releasesfullsend-ai/fullsend147—~3.5kAutomated safety check: PassApache-2.0

Similar skills

  • Aspire

    microsoft/aspire.dev

    Official

    Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.

    196 GitHub starsUsed in 4 repos~1.1k tokens
    DevOps & CloudAuto-check passed

  • Release

    bmeares/Meerschaum

    Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.

    154 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Google Agents CLI Scaffold

    pifferologo/cloud-agents-cli

    This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or…

    129 GitHub starsUsed in 1 repo~2.9k tokens
    DevOps & CloudAuto-check: notes

  • Agr Release

    computerlovetech/agr

    Release process for the agr package. An agent skill from computerlovetech/agr.

    451 GitHub stars~1.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Cutting Releases

    fullsend-ai/fullsend

    A skill your agent uses when the user wants to tag a release, cut a release candidate, or ship a new version.

    147 GitHub stars~3.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • AI Server

    Opentrons/opentrons

    Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment.

    521 GitHub stars~2.5k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

Categories

Questions about Deploy Process

What does Deploy Process do?

Release process for indexion. An agent skill from trkbt10/indexion. Deploy Process is an agent skill from trkbt10/indexion. Release process for indexion.

When should I use Deploy Process?

Deploy Process fits situations like: the user asks to release; tasks that involve Deployment.

How do I install Deploy Process in Claude Code?

Run `npx skills add trkbt10/indexion --skill deploy-process -a claude-code`. Or copy the skill folder (.claude/skills/deploy-process in trkbt10/indexion) into .claude/skills/deploy-process in your project. Claude Code loads it when a task matches its description.

How do I install Deploy Process in Codex?

Run `npx skills add trkbt10/indexion --skill deploy-process -a codex`. Or copy the skill folder (.claude/skills/deploy-process in trkbt10/indexion) into .agents/skills/deploy-process in your project. Codex loads it when a task matches its description.

Can I use Deploy Process 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 trkbt10/indexion --skill deploy-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-process, .gemini/skills/deploy-process, .github/skills/deploy-process and .opencode/skills/deploy-process in your project.

What does Deploy Process need to run?

Going by SKILL.md and its folder, Deploy Process needs the command-line tools its instructions call (git, bun and bash).

Does Deploy Process access the network?

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

Is Deploy Process 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. Review the folder before installing.

What licence does Deploy Process use?

Deploy Process 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 Deploy Process use?

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Deploy Process?

Skills that share tags, products or a category with Deploy Process: Aspire (microsoft/aspire.dev, 196 stars), Release (bmeares/Meerschaum, 154 stars), Google Agents CLI Scaffold (pifferologo/cloud-agents-cli, 129 stars) and Agr Release (computerlovetech/agr, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deploy Process?

trkbt10 (a GitHub user) maintains it in trkbt10/indexion, which has 153 GitHub stars. The repository was last updated on September 22, 2026.

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