npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

fdnqa

v1.4.1

Published

QA Agentic Workflows for OpenCode — 9router edition

Readme

QA Agentic Workflows (OpenCode)

Kumpulan agentic workflow OpenCode yang fokus untuk kebutuhan Quality Assurance. Satu orchestrator sebagai pintu masuk, mendistribusikan permintaan user ke salah satu dari lima workflow QA — setiap workflow punya pipeline tetap: planner → debater → implementor → reviewer.

Struktur Repo

qa-agentic-workflows/
├── opencode.json                     # konfigurasi global OpenCode
├── AGENTS.md                         # instruksi proyek untuk semua agent
├── docs/
│   └── workflow-guide.md             # detail tiap workflow + cara pakai
└── .opencode/
    └── agent/
        ├── orchestrator.md           # primary agent, pintu masuk user
        ├── test-case-generator/
        │   ├── planner.md
        │   ├── debater.md
        │   ├── implementor.md
        │   └── reviewer.md
        ├── web-automation/
        │   └── ... (4 file sama seperti di atas)
        ├── mobile-automation/
        │   └── ...
        ├── api-automation/
        │   └── ...
        └── performance-test/
            └── ...

Lima Workflow QA

| Workflow | Fokus | |---|---| | test-case-generator | Requirement/PRD/user story → test case terstruktur (manual, Gherkin/BDD, atau format tool seperti TestRail/Xray) | | web-automation | Skrip automation testing web (Playwright/Selenium/Cypress, Page Object Model) | | mobile-automation | Skrip automation testing mobile (Appium/Espresso/XCUITest) | | api-automation | Skrip automation testing API/backend (contract, integration, negative testing) | | performance-test | Skrip load/stress/spike test (k6/JMeter/Gatling) + strategi threshold |

Setiap workflow punya 4 subagent dengan peran tetap:

  • planner — menyusun strategi/rencana berdasarkan konteks dari user.
  • debater — mengkritik rencana planner secara adversarial, idealnya berjalan di model/provider berbeda supaya kritiknya independen.
  • implementor — mengeksekusi rencana yang sudah didebat menjadi deliverable konkret (write/edit/bash diizinkan).
  • reviewer — quality gate terakhir, read-only (tidak bisa edit/write/bash), hanya memberi catatan temuan.

Cara Pakai

Install

npm install -g fdnqa
fdnqa install

Perintah fdnqa install akan:

  • Menyalin agent files ke ~/.config/opencode/agents/
  • Menulis provider config ke ~/.config/opencode/opencode.jsonc
  • Menambahkan env vars ke shell RC file (.zshrc / .bashrc)

Setelah selesai, jalankan source ~/.zshrc (atau .bashrc) untuk mengaktifkan perubahan.

Uninstall

fdnqa uninstall
npm uninstall -g fdnqa

Jalankan fdnqa uninstall sebelum npm uninstall untuk memastikan semua agent files dan konfigurasi dibersihkan dengan benar.

Penggunaan

  1. Install OpenCode: lihat dokumentasi resmi untuk instruksi terbaru sesuai OS Anda.
  2. Cek model yang tersedia di akun Anda dengan opencode models, lalu sesuaikan field model: di tiap file agent (lihat bagian Penting: Sesuaikan Model di bawah).
  3. Mulai percakapan dengan agent orchestrator (agent default/primary), sampaikan kebutuhan QA Anda — orchestrator akan memilih workflow yang sesuai dan menjalankan pipeline empat tahap secara otomatis.

Contoh permintaan ke orchestrator:

"Ini PRD fitur checkout saya, tolong buatkan test case-nya dalam format Gherkin."

"Tolong buatkan skrip Playwright untuk flow login dan lupa password di web kami."

"Saya butuh load test untuk endpoint /api/orders dengan target 500 RPS."

Penting: Sesuaikan Model

ID model di setiap file .md (anthropic/claude-opus-4-8, anthropic/claude-sonnet-5, openai/gpt-5.1, dst.) adalah contoh default mengikuti prinsip tiering:

  • Orchestrator & planner → model kelas atas, reasoning/strategi kuat.
  • Debater → model kelas atas dari provider berbeda dari planner, supaya kritiknya benar-benar independen dan bukan sekadar menyetujui.
  • Implementor → model kelas menengah, cukup kuat untuk menulis kode/test case dengan detail.
  • Reviewer → model kelas menengah, permission read-only.

Ketersediaan model berubah dari waktu ke waktu dan tergantung provider yang Anda hubungkan ke OpenCode. Jalankan opencode models sebelum mulai, lalu sesuaikan field model: di setiap file agent bila perlu.

Kustomisasi Lanjutan

  • Ingin menambah workflow QA baru (misalnya accessibility-testing atau security-testing)? Duplikasi salah satu folder workflow di .opencode/agent/, sesuaikan isi 4 file peran-nya, lalu tambahkan workflow tersebut ke daftar di orchestrator.md.
  • Ingin mengubah permission (misalnya implementor perlu akses bash lebih longgar untuk menjalankan test suite otomatis), edit bagian permission: di frontmatter file agent terkait.
  • Detail lengkap tiap tugas per role ada di docs/workflow-guide.md.