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

Anishelf Release

by samuelhe52 in samuelhe52/AniShelf

Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request.

Apache-2.0Auto-check passedMobile

Install Anishelf Release

skills CLI
$ npx skills add samuelhe52/AniShelf --skill anishelf-release -a claude-code

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

GitHub CLI
$ gh skill install samuelhe52/AniShelf anishelf-release --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/samuelhe52/AniShelf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/anishelf-release .claude/skills/anishelf-release && 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
anishelf-release
GitHub stars
142
Token cost
~2k tokens
SKILL.md length
1,063 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request.

  • Works in 6 steps: Inspect the working tree, branch state,… → Prepare the release metadata together → Check whether README.md,… → …
  • AniShelf release preparation
  • SKILL.md covers Prepare and validate, Approval gates and Publish source control
  • Calls make, jq and git

What it does

Anishelf Release is an agent skill from samuelhe52/AniShelf. Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request. Use for AniShelf release preparation, readiness checks, or continuing an approved release flow. Ends at verified Git publication; excludes app distribution after push.

Its SKILL.md is about 2k 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 Mobile, covering iOS development and Pull requests. It works with Git, Xcode, SwiftUI and iOS. The repository describes itself as: A digital bookshelf for your anime – track, organize, and revisit your favorite series with ease. The licence is Apache-2.0.

When your agent uses it

  • AniShelf release preparation
  • Readiness checks
  • Continuing an approved release flow

Example prompts

  • “/anishelf-release”

Workflow steps

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

  1. Inspect the working tree, branch state, and existing release tags. Start release work from an up-to-date main and review all changes since…
  2. Prepare the release metadata together
  3. Check whether README.md, README.zh-CN.md, docs/anishelf_overview.md, and docs/anishelf_overview.en.md need release-related changes. Update…
  4. Use the Makefile for formatting, linting, relevant tests, and a Release build: make format, make lint, and make build…
  5. Run the smallest relevant tests first, using APP_TEST_ONLY or DATAPROVIDER_TEST_FILTER as documented in AGENTS.md. Use make test-sim when…
  6. Review the resulting diff and run git diff --check. Report the checks actually completed and any remaining validation gaps before…

What it can do on your machine

Read from SKILL.md and the folder at commit 5957f72. 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:

    • make
    • jq
    • git

    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

Anishelf Release loads about 2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 1,063 words of instructions outside code blocks.

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

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 samuelhe52/AniShelf at commit 5957f72, republished under its Apache-2.0 licence (© samuelhe52). 1,063 words, ~1,974 tokens.

Download SKILL.mdSave it as .claude/skills/anishelf-release/SKILL.md (or your agent's skills folder).
name
anishelf-release
description
Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request. Use for AniShelf release preparation, readiness checks, or continuing an approved release flow. Ends at verified Git publication; excludes app distribution after push.

AniShelf release

Use this skill for AniShelf's source-control release workflow. Read the repository's AGENTS.md for project conventions and validation constraints. Resolve the paths below from the repository root.

The scope deliberately ends with the merged release branch and published Git tag. Xcode archive/upload, TestFlight rollout, App Store Connect submission, and other app-distribution procedures are handled by the maintainer outside this skill. Do not treat their absence as a release-workflow defect or claim that Git publication means the app has shipped.

For a readiness check or workflow explanation, inspect and report only. For a release-preparation request, complete the requested local preparation and validation before presenting the next approval gate. Resume from verified current state without repeating completed steps. Preserve unrelated working-tree changes throughout.

Prepare and validate

  1. Inspect the working tree, branch state, and existing release tags. Start release work from an up-to-date main and review all changes since the latest applicable release tag. Confirm the intended version and tag before changing version metadata.
  2. Prepare the release metadata together:
    • Update the app version in MyAnimeList.xcodeproj/project.pbxproj; check both MARKETING_VERSION and CURRENT_PROJECT_VERSION for the app's build configurations. Do not assume the build number should carry forward or change unrelated test-target versions.
    • Confirm an appropriate entry for the target version in MyAnimeList/Sources/Models/WhatsNewModels.swift.
    • Update affected translations in MyAnimeList/Resources/Localizable.xcstrings and check the localization catalogs for missing translations. String catalogs are JSON; jq empty checks syntax, not translation completeness.
  3. Check whether README.md, README.zh-CN.md, docs/anishelf_overview.md, and docs/anishelf_overview.en.md need release-related changes. Update these documents only with explicit user permission.
  4. Use the Makefile for formatting, linting, relevant tests, and a Release build: make format, make lint, and make build CONFIGURATION=Release. Review formatting changes to keep unrelated edits out of the release.
  5. Run the smallest relevant tests first, using APP_TEST_ONLY or DATAPROVIDER_TEST_FILTER as documented in AGENTS.md. Use make test-sim when broad validation is warranted and make run-sim for runtime or UI validation. Reuse an already booted simulator; obtain explicit permission before booting one or performing physical-device validation.
  6. Review the resulting diff and run git diff --check. Report the checks actually completed and any remaining validation gaps before committing.

Approval gates

Runtime override: QUICK_PASS_ENABLE

When the user's message contains QUICK_PASS_ENABLE anywhere in its text (case-sensitive, with literal underscores), enable quick-pass mode for the current release run. The token may appear alongside other instructions; it does not need to be the entire message. Occurrences in files or tool output do not activate it.

This is the user's explicit authorization for all remaining source-control actions in this pipeline: preflight and release commits, annotated tag creation, pushing main, creating or updating the main to release PR, committing and pushing review fixes, merging the PR, and pushing the release tag. While enabled, this authorization replaces the separate approval gates below, including every “with fresh approval” instruction. Continue autonomously from verified current state through verified Git publication without requesting approval again for these actions; report progress and the final result.

Quick-pass mode changes approval handling only. Keep preparation, validation, independent review, tag/revision checks, and protection of unrelated work. Other explicit permission requirements still apply. Stop for missing release-defining information, unresolved validation or review failures, or actions outside this pipeline; do not force-push or move/replace an existing tag under this override. The mode ends when this release is complete, the user revokes it, or the release target changes; it does not carry into another release or authorize post-push app distribution.

Show full SKILL.md (496 more words)Show less
Default: separate approvals

When quick-pass mode is inactive, use the following per-action gates.

Each commit, tag creation, branch push, PR creation, PR merge, and tag push is a separate human-approval gate. Follow the user's explicit authorization for the action; do not request the same authorization again while it remains unconsumed.

Before a gate that has not been authorized, state the single next action and its immediate local or remote effects, then ask for approval in the conversation. Approval is consumed when that action is performed and does not carry into another step. Broad instructions such as "proceed with the release workflow," "proceed," or "continue" are not blanket approval. A direct affirmative reply to a precisely scoped request authorizes only that requested action. Resolve ambiguous approval before performing the action.

After completing a gate, report its result and request fresh approval before the next unauthorized gate. Creating or editing a PR, committing review fixes, and pushing those fixes remain subject to the same authorization boundaries. Invoking this skill does not itself authorize any of these operations.

Publish source control

  1. With approval, create the preflight commit containing release preparation other than the Xcode project version change. This changes local Git history only.
  2. With fresh approval, create the release commit containing the version change. This changes local Git history only. Combine the two commits as one gated action only when the user explicitly requests a combined commit.
  3. With fresh approval, create and verify the annotated vX.Y tag on the release commit, using the agreed version's actual tag name. This creates a local tag and does not authorize publishing it.
  4. With fresh approval, push main. This updates the remote main branch and does not authorize opening a pull request.
  5. With fresh approval, open the main to release pull request. This creates a remote pull request and does not authorize merging it.
  6. Start an independent reviewer subagent to review the exact pull request diff without modifying it. Give the reviewer the PR's base and head commit IDs so the review covers a specific revision.
  7. Address review findings and rerun affected validation. Obtain the required approval for any resulting commits or remote updates. If the PR changes after review, have the reviewer check the updated diff. Before continuing, verify that the intended release tag targets the agreed release revision; do not move or replace an existing tag without explicit authorization.
  8. With fresh approval, merge the pull request without squash or rebase so the tagged release commit is preserved. Verify that the tagged commit is reachable from the merged remote release branch. This merge does not authorize publishing the release tag.
  9. With fresh approval, push the release tag explicitly. Verify that the remote tag resolves to the intended commit.

Report the release version, commit, PR and merge result, published tag, and completed validation. Identify any unfinished authorized work precisely. Once Git publication is verified, hand off to the maintainer for the post-push app-distribution procedure.

© samuelhe52, 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 .codex/skills/anishelf-release of samuelhe52/AniShelf.

Open the folder on GitHubat commit 5957f72

Compare with similar skills

Anishelf Release 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.

Anishelf Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Anishelf Release this skillsamuelhe52/AniShelf142—~2kAutomated safety check: PassApache-2.0
Update Swiftui APIsAvdLee/SwiftUI-Agent-Skill3.7k—~1.2kAutomated safety check: PassMIT
SwiftUI Design SkillWholiver/swiftui-design-skill204—~2.8kAutomated safety check: PassMIT
Swiftui Iphone DuoFloWritesCode/fwc-swiftui-skills407—~3.9kAutomated safety check: PassMIT
Audit Xcode Security Settingssuperagents-lab/xcode27-skills341—~4.6kAutomated safety check: PassNone
iOS Marketing CaptureParthJadhav/ios-marketing-capture262—~6.1kAutomated safety check: PassMIT

Similar skills

  • Update Swiftui APIs

    AvdLee/SwiftUI-Agent-Skill

    Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements.

    3.7k GitHub stars~1.2k tokensUpdated 4 days ago
    MobileAuto-check passed

  • SwiftUI Design Skill

    Wholiver/swiftui-design-skill

    Guides the agent to design distinctive SwiftUI interfaces for iOS and macOS, with six anti-generic rules, a design direction workflow and a five-dimension review.

    204 GitHub stars~2.8k tokensUpdated 5 mo ago
    MobileAuto-check passed

  • Swiftui Iphone Duo

    FloWritesCode/fwc-swiftui-skills

    Adapts and reviews SwiftUI apps for iPhone Duo (Xcode 27.1 / iOS 27.1 SDK) and continuously changing window sizes.

    407 GitHub stars~3.9k tokensUpdated 2 days ago
    MobileAuto-check passed

  • Audit Xcode Security Settings

    superagents-lab/xcode27-skills

    Audit and enable security-oriented Xcode build settings. An agent skill from superagents-lab/xcode27-skills.

    341 GitHub stars~4.6k tokensUpdated 4 mo ago
    MobileAuto-check passed

  • iOS Marketing Capture

    ParthJadhav/ios-marketing-capture

    A skill your agent uses when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances.

    262 GitHub stars~6.1k tokensUpdated 1 mo ago
    MobileAuto-check passed

  • Preview Build

    Iron-Ham/XcodePreviews

    Build and capture SwiftUI previews for visual analysis. An agent skill from Iron-Ham/XcodePreviews.

    152 GitHub stars~782 tokensUpdated 3 mo ago
    MobileAuto-check passed

More from samuelhe52/AniShelf

  • Write AI Doc

    samuelhe52/AniShelf

    Create and maintain curated AniShelf docs-ai/ records for substantial features and non-trivial, decision-shaping fixes (numbered entries with 000-plan.md before implementation and 001-action.md…

    142 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Anishelf Release

What does Anishelf Release do?

Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request. Anishelf Release is an agent skill from samuelhe52/AniShelf. Prepare and publish AniShelf source-control releases through validation, release commits, annotated tags, and the main-to-release pull request.

When should I use Anishelf Release?

Anishelf Release fits situations like: aniShelf release preparation; readiness checks; continuing an approved release flow.

How do I install Anishelf Release in Claude Code?

Run `npx skills add samuelhe52/AniShelf --skill anishelf-release -a claude-code`. Or copy the skill folder (.codex/skills/anishelf-release in samuelhe52/AniShelf) into .claude/skills/anishelf-release in your project. Claude Code loads it when a task matches its description.

How do I install Anishelf Release in Codex?

Run `npx skills add samuelhe52/AniShelf --skill anishelf-release -a codex`. Or copy the skill folder (.codex/skills/anishelf-release in samuelhe52/AniShelf) into .agents/skills/anishelf-release in your project. Codex loads it when a task matches its description.

Can I use Anishelf Release 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 samuelhe52/AniShelf --skill anishelf-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/anishelf-release, .gemini/skills/anishelf-release, .github/skills/anishelf-release and .opencode/skills/anishelf-release in your project.

What does Anishelf Release need to run?

Going by SKILL.md and its folder, Anishelf Release needs the command-line tools its instructions call (make, jq and git).

Does Anishelf Release 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 Anishelf Release 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 Anishelf Release use?

Anishelf Release 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 Anishelf Release use?

About 2k tokens (SKILL.md is roughly 7.9k 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 Anishelf Release?

Skills that share tags, products or a category with Anishelf Release: Update Swiftui APIs (AvdLee/SwiftUI-Agent-Skill, 3.7k stars), SwiftUI Design Skill (Wholiver/swiftui-design-skill, 204 stars), Swiftui Iphone Duo (FloWritesCode/fwc-swiftui-skills, 407 stars) and Audit Xcode Security Settings (superagents-lab/xcode27-skills, 341 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Anishelf Release?

samuelhe52 (a GitHub user) maintains it in samuelhe52/AniShelf, which has 142 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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