Agent skill

Oidc Release

by H2CK in H2CK/oidc

Prepare and verify a new release for the Nextcloud OIDC Identity Provider app.

AGPL-3.0Auto-check passedBackend & APIs

Install Oidc Release

skills CLI
$ npx skills add H2CK/oidc --skill oidc-release -a claude-code

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

GitHub CLI
$ gh skill install H2CK/oidc oidc-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/H2CK/oidc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/oidc-release .claude/skills/oidc-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
oidc-release
GitHub stars
135
Token cost
~2k tokens
SKILL.md length
691 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Prepare and verify a new release for the Nextcloud OIDC Identity Provider app.

  • Works in 6 steps: Version Input → Date Input → Update Version Files → …
  • Tasks that involve OAuth and OpenID Connect
  • SKILL.md covers What This Skill Does, Usage Examples, Requirements and Implementation Details, plus 5 more sections
  • Calls git and make

What it does

Oidc Release is an agent skill from H2CK/oidc. Prepare and verify a new release for the Nextcloud OIDC Identity Provider app. Automatically updates version files, generates changelog entries from merge requests, and verifies the build.

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 Backend & APIs, covering OAuth and OpenID Connect. It works with Git. The repository describes itself as: OpenID Connect App for Nextcloud. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve OAuth and OpenID Connect

Example prompts

  • “/oidc-release”

Requirements

  • Node.js

Workflow steps

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

  1. Version Input
  2. Date Input
  3. Update Version Files
  4. Generate Changelog Entry
  5. Build Verification
  6. Summary and Next Steps

What it can do on your machine

Read from SKILL.md and the folder at commit 447c6a7. 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
    • make

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

  • Network

    Links to these hosts (documentation or services it may open):

    • semver.org
    • keepachangelog.com

    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

Oidc Release loads about 2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 691 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
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 H2CK/oidc at commit 447c6a7, republished under its AGPL-3.0 licence (© H2CK). 691 words, ~2,036 tokens.

Download SKILL.mdSave it as .claude/skills/oidc-release/SKILL.md (or your agent's skills folder).
name
oidc-release
description
Prepare and verify a new release for the Nextcloud OIDC Identity Provider app. Automatically updates version files, generates changelog entries from merge requests, and verifies the build.
short_description
Prepare OIDC app release
tags
nextcloud, oidc, release, automation

OIDC Identity Provider Release Preparation Skill

This skill automates the process of preparing a new release for the Nextcloud OIDC Identity Provider application. It handles version updates across multiple files, generates changelog entries from Git merge requests, and verifies the build process.

What This Skill Does

When invoked, this skill performs the following steps:

1. Version Input
  • If a version is provided via parameter, use it
  • Otherwise, prompt the user for the new version number
  • Validates the version follows semantic versioning (X.Y.Z) format
  • Shows current version from appinfo/info.xml for reference
2. Date Input
  • If a date is provided via parameter, use it
  • Otherwise, defaults to today's date in YYYY-MM-DD format
3. Update Version Files

Updates the version number in:

  • appinfo/info.xml - Nextcloud app info file
  • package.json - Node.js package file
  • package-lock.json - Node.js lock file (both root and package entries)
4. Generate Changelog Entry
  • Extracts the last release date from CHANGELOG.md
  • Searches Git history for merge commits and pull request references since the last release
  • Groups changes into "Added" and "Changed" categories
  • Creates a properly formatted markdown entry with:
    • Version number and release date
    • Pull request references as links
    • Standard entries for dependency updates and translations
5. Build Verification
  • Executes make build-test to:
    • Clean previous build artifacts
    • Run unit and integration tests
    • Build production JavaScript bundles
    • Assemble the release package
6. Summary and Next Steps
  • Displays a summary of all changes made
  • Shows next steps for the release process:
    • Review changes with git diff
    • Commit changes
    • Create Git tag
    • Push to repository

Usage Examples

Interactive Mode (prompts for version)
use skill oidc-release
prepare-release
With Version Parameter
use skill oidc-release
prepare-release version=1.18.0
With Version and Date
use skill oidc-release
prepare-release version=1.18.0 date=2026-06-15
As One-Liner
use skill oidc-release && prepare-release version=1.18.0

Requirements

Working Directory

The skill should be invoked from the OIDC app directory:

cd /path/to/nextcloud/server/apps/oidc

Or it will automatically detect the app directory structure.

Required Files
  • appinfo/info.xml - Must exist with current version
  • package.json - Must exist
  • package-lock.json - Must exist
  • CHANGELOG.md - Must exist with previous releases
  • Makefile - Must have build-test target
Required Tools
  • git - For accessing commit history and merge requests
  • sed - For file modifications
  • grep - For pattern matching
  • awk - For text processing
  • make - For build process
  • npm - For JavaScript dependencies

Implementation Details

Version Detection

The current version is automatically detected from appinfo/info.xml using:

bash
grep -oP '<version>\K[^<]+' appinfo/info.xml
Merge Request Discovery

The skill searches for pull request references in commit messages using:

bash
git log --oneline --since="$last_release_date" --format="%s" | grep -oE '#[0-9]+'

This captures PR numbers from commit messages like:

  • Merge pull request #653 from H2CK:feat_extend-access-token
  • Fixes #123
  • Related to #456
File Updates

All file updates are performed with sed in-place edits. The skill:

  1. Creates backups automatically (on macOS with sed -i '')
  2. Validates changes were applied correctly
  3. Reports success/failure for each file
Show full SKILL.md (269 more words)Show less
Changelog Generation

The changelog entry is inserted at the top of the file, below the header, maintaining:

  • Consistent markdown formatting
  • Proper date format (YYYY-MM-DD)
  • Link formatting for PR references
  • Categorization of changes (Added/Changed)

Error Handling

The skill includes comprehensive error handling:

  • Validates version format (optional, with user confirmation)
  • Checks for required files existence
  • Validates Git repository status
  • Verifies build process completion
  • Provides clear error messages with color coding

Color Output

The skill uses color-coded output for better visibility:

  • Red - Errors and failures
  • Green - Success messages
  • Yellow - Information and warnings

Customization

To customize the behavior, you can:

  1. Modify the changelog template - Edit the skill to change how changelog entries are formatted
  2. Add more categories - Extend to support "Fixed", "Removed", "Security" sections
  3. Add pre-release checks - Include additional validation steps
  4. Integrate with CI/CD - Extend to automatically create Git tags or push changes

Notes

  • The skill is designed for the Nextcloud OIDC Identity Provider app but can be adapted for other Nextcloud apps
  • It assumes semantic versioning (MAJOR.MINOR.PATCH)
  • The release date format follows ISO 8601 (YYYY-MM-DD)
  • Pull request references are formatted as GitHub links

Troubleshooting

"Version not found" error

Ensure appinfo/info.xml exists and has a <version> tag. Run from the correct directory.

"No merge requests found" warning

This is normal if there are no PRs between releases. The changelog will still be created with standard entries.

"Build failed" error

Check the output of make build-test for specific errors. Ensure all dependencies are installed.

Permission denied errors

Make sure the script has write permissions for all files:

bash
chmod +x build/prepare-release.sh
chmod u+w appinfo/info.xml package.json package-lock.json CHANGELOG.md

See Also


Workflow Implementation

STEP 1: Initialize
├─ Detect current working directory
├─ Verify required files exist
├─ Get current version from info.xml
└─ Load skill configuration

STEP 2: Get Version
├─ Check if version parameter provided
├─ If not, prompt user for version
├─ Validate version format (optional)
└─ Store version for subsequent steps

STEP 3: Get Release Date
├─ Check if date parameter provided
├─ If not, use today's date
└─ Format as YYYY-MM-DD

STEP 4: Discover Changes
├─ Extract last release date from CHANGELOG.md
├─ Search Git log for commits since last release
├─ Extract pull request numbers from commit messages
└─ Format PR references

STEP 5: Update Version Files
├─ Update appinfo/info.xml
│  └─ Replace <version>X.Y.Z</version> with new version
├─ Update package.json
│  └─ Replace "version": "X.Y.Z" with new version
└─ Update package-lock.json
   ├─ Update root package version
   └─ Update top-level version

STEP 6: Update CHANGELOG.md
├─ Create new entry header with version and date
├─ Add "Added" section (if applicable)
├─ Add "Changed" section
│  ├─ List pull request references
│  ├─ Add "Updated dependencies"
│  └─ Add "Updated translations"
└─ Insert entry at top of changelog

STEP 7: Verify Build
├─ Run "make build-test"
├─ Check return code
├─ Capture output for error reporting
└─ Display success/failure

STEP 8: Finalize
├─ Display summary of changes
├─ Show next steps
└─ Return to user control

© H2CK, AGPL-3.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 .agents/skills/oidc-release of H2CK/oidc.

Open the folder on GitHubat commit 447c6a7

Compare with similar skills

Oidc 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.

Oidc Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oidc Release this skillH2CK/oidc135—~2kAutomated safety check: PassAGPL-3.0
Flow Next Workgmickel/flow-next707—~1.9kAutomated safety check: PassMIT
Python Pypi Package Buildergithub/awesome-copilot40k1 repos~4.6kAutomated safety check: PassMIT
Antipattern Preventiondoorkeeper-gem/doorkeeper5.5k—~1.1kAutomated safety check: PassMIT
Add Patterndevlint/GitWand180—~2.3kAutomated safety check: PassMIT
Add Resolverdevlint/GitWand180—~1.6kAutomated safety check: PassMIT

Similar skills

  • Flow Next Work

    gmickel/flow-next

    Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow.

    707 GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    DevelopmentAuto-check passed
  • Antipattern Prevention

    doorkeeper-gem/doorkeeper

    Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.

    5.5k GitHub stars~1.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Add Pattern

    devlint/GitWand

    Add a new conflict-resolution pattern to GitWand core. An agent skill from devlint/GitWand.

    180 GitHub stars~2.3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Add Resolver

    devlint/GitWand

    Add a format-specific resolver to GitWand core. An agent skill from devlint/GitWand.

    180 GitHub stars~1.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Squash Bugbot

    LFDT-Lineth/lineth-monorepo

    Triage unresolved bot review comments on a GitHub PR. An agent skill from LFDT-Lineth/lineth-monorepo.

    126 GitHub stars~3.3k tokensUpdated today
    Backend & APIsAuto-check passed

Works with

Questions about Oidc Release

What does Oidc Release do?

Prepare and verify a new release for the Nextcloud OIDC Identity Provider app. Oidc Release is an agent skill from H2CK/oidc. Prepare and verify a new release for the Nextcloud OIDC Identity Provider app.

When should I use Oidc Release?

Oidc Release fits situations like: tasks that involve OAuth and OpenID Connect.

How do I install Oidc Release in Claude Code?

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

How do I install Oidc Release in Codex?

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

Can I use Oidc 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 H2CK/oidc --skill oidc-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/oidc-release, .gemini/skills/oidc-release, .github/skills/oidc-release and .opencode/skills/oidc-release in your project.

What does Oidc Release need to run?

Going by SKILL.md and its folder, Oidc Release needs the command-line tools its instructions call (git and make). Our summary lists: Node.js.

Does Oidc Release access the network?

SKILL.md names 2 domains. As links in the text: semver.org and keepachangelog.com. This is read from the text; nothing was executed.

Is Oidc 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 Oidc Release use?

Oidc Release is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oidc Release use?

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

Skills that share tags, products or a category with Oidc Release: Flow Next Work (gmickel/flow-next, 707 stars), Python Pypi Package Builder (github/awesome-copilot, 40k stars), Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars) and Add Pattern (devlint/GitWand, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oidc Release?

H2CK (a GitHub user) maintains it in H2CK/oidc, which has 135 GitHub stars. The repository was last updated on October 8, 2026.

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