agentleFS
Sign inStart free
roedyrustamroedyrustam/doku-gemini-mcp/skills/upgrade/SKILL.md

upgrade

Skill2 starsChanged 9 days agoMITView on GitHub

Diff existing DOKU client implementation against latest API spec version, patching only changed files and signature formats / Bandingkan dan perbarui implementasi DOKU ke versi spesifikasi API terbaru.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use new, context and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 4 projects that use this

  • aegiswizardSkill

    context

    Also in 3 projects that use this

  • MicrosoftSkill

    init

    Also in 6 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 5 projects that use this

  • tuistSkill

    migrate

    Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

    Also in 3 projects that use this

  • imehrSkill

    frontend

    Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns and quality standards

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search workspace for DokuService, dokuClient, /checkout/v1/payment, /doku-virtual-account/v2, /snap-adapter.

    line 30
  2. Very specific:

    Check endpoint path versions (v1 vs v2 vs snap-adapter).

    line 33
  3. Distinctive:

    Check signature assembly for missing header fields or trailing newlines.

    line 34
  4. Very specific:

    Check webhook verification formula (crypto.timingSafeEqual usage).

    line 35
  5. Very specific:

    MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: …

    line 60

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upgrade / Pembaruan Klien DOKU

English | Bahasa Indonesia

<a name="english"></a>

English

Description

Analyzes existing project codebase for DOKU integration files, compares endpoint paths and signature generation code against the latest DOKU Jokul API v2 and SNAP API v1.0 specs, and applies minimal non-breaking code patches.

Trigger Conditions

Activate this skill when the user says:

  • "upgrade DOKU client"
  • "update DOKU API version"
  • "patch DOKU integration"

Step-by-Step Execution Protocol

  1. Locate Existing DOKU Integration Files:
    • Search workspace for DokuService, dokuClient, /checkout/v1/payment, /doku-virtual-account/v2, /snap-adapter.
  2. Diff Against .doku-spec.json / Standard Rules:
    • Check endpoint path versions (v1 vs v2 vs snap-adapter).
    • Check signature assembly for missing header fields or trailing newlines.
    • Check webhook verification formula (crypto.timingSafeEqual usage).
  3. Apply Targeted Code Patches:
    • Modify only changed functions or endpoints without breaking existing method signatures.

<a name="bahasa-indonesia"></a>

Bahasa Indonesia

Deskripsi

Menganalisis berkas integrasi DOKU pada codebase proyek, membandingkan path endpoint dan kode pembuatan signature terhadap spesifikasi DOKU API terbaru, dan menerapkan patch kode minimal tanpa merusak fungsi yang sudah ada.

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "upgrade DOKU client"
  • "perbarui versi DOKU API"
  • "patch integrasi DOKU"

🚨 SNAP Integration Mandate (CRITICAL)

MANDATORY: The AI Agent MUST automatically apply the SNAP API v1.0 standard (Standard Nasional Open API Pembayaran) for all DOKU integrations, instead of the legacy Jokul API v2, unless the user explicitly requests otherwise. All generated signatures, headers, and endpoints MUST follow the SNAP BI standard.

🧪 DOKU Sandbox Simulator

MANDATORY: When testing in Sandbox mode and needing to access the Payment Simulator, the AI Agent MUST use this exact URL: https://sandbox.doku.com/gtw-config-v2/simulator.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free