← all publishers

Jewgah

@jewgah source repo

Report this profile Claim this profile

• 12 skills
• 0 followers
• 1 day ago last updated

1. ▌
   Commit · jewgah

   Commit staged changes, update CLAUDE.md and memory if relevant
   0 installs
2. ▌
   Loopit · jewgah

   Drive a task queue (loop-tasks.md) to completion in ANY repo. Detect the repo's own rules, then for each task plan -> /review-plan -> implement -> verify -> /review -> fix all findings -> /battle-test -> commit -> push -> client doc -> mark done. Each task runs in its OWN subagent (context isolation, token-cheap); the main session only orchestrates. Autonomous between tasks; pauses only for genuine product decisions.
   0 installs
3. ▌
   Review · jewgah

   Review code changes for flaws, bugs, security issues, and potential problems
   0 installs
4. ▌
   Choices · jewgah

   Summarize the open decisions/choices from the current conversation into a simple, copy-paste WhatsApp message for the team to weigh in on. Use when work is blocked on product/scope decisions a human must make.
   0 installs
5. ▌
   Loopable · jewgah

   Find recurring work worth automating, then take the top candidate through the full delivery flow — plan, /review-plan, implement, /review-deep, fix all findings, commit, and file a ticket in ~/Downloads/tickets/{project}/.
   0 installs
6. ▌
   Sessions · jewgah bundle

   List recent Claude Code sessions across all projects with project name, session ID, resume command, and short description of what the session was about. Handles multiple parallel sessions per project. Use when the user wants to find, resume, or recall a previous Claude conversation — especially before/after a reboot.
   0 installs
7. ▌
   Vulgarize · jewgah

   Turn the technical changes in the working tree into a short, casual, jargon-free message you can send straight to the client (en/fr)
   0 installs
8. ▌
   Battle Test · jewgah

   Run the frontend and backend checks that CAN actually be run for the current change, then report what ran, a battle-tested score out of 100, and the checks that still need a human. Use after implementing a feature or a bugfix and before committing it: "test this", "run the tests", "did I break anything", "how solid is this change", "what still needs manual testing", "teste ça", "est-ce que c'est bien testé". Runs the repo's own tooling only, never a new framework. It reports; it never commits, pushes, or deploys.
   0 installs
9. ▌
   Init Agents · jewgah bundle

   Scaffold a tailored Claude Code agent team into the current repo — detects the stack, proposes agents/commands/hooks, then writes and wires them into .claude/ and CLAUDE.md.
   0 installs
10. ▌
    Review Deep · jewgah

    Deep multi-agent code review — parallel agents cross-check each other to catch critical bugs
    0 installs
11. ▌
    Security Audit · jewgah

    Audit the codebase for common security vulnerabilities (OWASP, secrets, auth, injection)
    0 installs
12. ▌
    Frontend Verify · jewgah bundle

    Verify frontend changes end to end after editing a web app, instead of manually clicking through pages. Use this whenever you have changed UI code and need to confirm nothing broke: "verify my frontend", "check the site after these edits", "did my UI break", "did my changes break anything", "make sure these routes still work", "smoke test the app", "check for console errors", "validate the pages I touched". Works with Next.js (app and pages router), React, Vite, and any local dev server. Built to be token cheap: it reads console errors and failed network requests first and writes full page state to disk, so it only pulls a snapshot or a screenshot into context when a route actually fails. Use it before saying a frontend change is done.
    0 installs