← all publishers

carofi-auto

@carofi-auto source repo

6 published skills

  1. Wd · carofi-auto bundle
    Post a work-done announcement to a Slack channel and create/update a Trello card, then log time to Clockify. Use after completing any task that produces PRs, fixes, or deployable changes. Supports --skip-time, --skip-post, --time <duration>, and --range-time for bulk backfill.
    0 installs
  2. Paymob · carofi-auto bundle
    Use when integrating Paymob payment processing — creating payment intentions, handling webhooks with HMAC validation, configuring checkout flows (hosted, embedded pixel, mobile SDK), or generating payment links. Covers MENA-region payment methods: cards (Visa/MC/Amex/MADA/OmanNet), digital wallets (Vodafone Cash, Orange Cash, e& money, stcPay, We Pay, Apple Pay, Google Pay), BNPL (Tabby, Tamara, vaLU, Sympl, Halan), and kiosk/cash.
    0 installs
  3. Triage · carofi-auto bundle
    Diagnose codebase issues from any input — ticket, freeform, paste. Traces the codebase autonomously, confirms root cause with evidence, outputs diagnosis, then waits for user to confirm before fixing. NO fixes before root cause is confirmed.
    0 installs
  4. Pr Review · carofi-auto
    Self-review your changes before raising a PR. Runs on your local branch/diff, scans every changed line for real bugs, security holes, missing tests, and design problems, filters false positives, and reports severity-tagged findings plus a ready-to-raise verdict. Triggers on "review my changes", "review my diff before I push", "is this ready to raise a PR", "self-review this branch".
    0 installs
  5. Feature Plan · carofi-auto bundle
    Use when feature discovery is complete and an execution-ready plan is needed. Triggers after /feature-discovery produces locked decisions, cleared risks, and defined success metrics. Do NOT use when critical unknowns remain — stop and run /feature-discovery first.
    0 installs
  6. Feature Discovery · carofi-auto bundle
    Use when you have a rough idea, feature request, initiative, or technical direction that hasn't been stress-tested yet. Triggers before brainstorming or planning, when assumptions are unexamined, scope is fuzzy, risks are unknown, or you need to find out what you don't know before committing to a direction.
    0 installs