agentleFS
roedyrustamroedyrustam/doku-gemini-mcp/skills/production-checklist/SKILL.md

production-checklist

Skill2 starsChanged 10 days agoMITView on GitHub

Run 8 mandatory production readiness checks before go-live deployment of DOKU Payment Gateway integration / Jalankan 8 pemeriksaan kesiapan produksi sebelum rilis integrasi DOKU.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. 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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Production Checklist / Checklist Kesiapan Produksi DOKU

English | Bahasa Indonesia


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

English

Description

Audits the codebase for 8 mandatory production security and reliability checks before switching from DOKU Sandbox (api-sandbox.doku.com) to Production (api.doku.com).

Trigger Conditions

Activate this skill when the user says:

  • "production checklist"
  • "check DOKU go-live readiness"
  • "audit DOKU production setup"

The 8 Mandatory Production Readiness Checks

#Check ItemRule / StandardStatus Audit Method
1Secrets SafetyNo hardcoded CLIENT_ID or SECRET_KEY in source files.Scan codebase for string literals matching DOKU keys.
2Signature StrictnessExact component string format without trailing newline \n.Inspect signature calculation assembly logic.
3Timestamp FormatUTC ISO8601 string without milliseconds (ends in Z).Check timestamp formatting function (.replace(/\.\d{3}Z$/, 'Z')).
4Webhook Signature VerificationReject unverified callback requests with HTTP 401 Unauthorized.Verify HMAC-SHA256 callback verifier implementation using crypto.timingSafeEqual.
5Webhook IdempotencyPrevent duplicate order fulfillment on repeated callback retries.Check database atomic state checks before order update.
6Log SanitizationNo customer PII or secret key leakage in application stdout/logs.Check log statements in payment and webhook handlers.
7Production Gateway URLDynamic switch between api-sandbox.doku.com and api.doku.com.Inspect DOKU_IS_PRODUCTION environment flag check.
8Error Exception SafetyStructured error responses without leaking node/stack traces to LLM context.Check error handler try-catch wrappers.

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

Bahasa Indonesia

Deskripsi

Melakukan audit kode terhadap 8 pemeriksaan keamanan dan keandalan wajib sebelum berpindah dari DOKU Sandbox (api-sandbox.doku.com) ke Production (api.doku.com).

Kondisi Pemicu

Aktifkan skill ini ketika pengguna mengatakan:

  • "production checklist"
  • "periksa kesiapan go-live DOKU"
  • "audit konfigurasi produksi 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.