Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

osherboudara99

@osherboudara99 source repo

8 published skills

  1. ▌
    Poll Codex Comments · osherboudara99 bundle
    Use after opening or updating a GitHub PR that has the chatgpt-codex-connector[bot] automated reviewer enabled. Polls the PR's review comments until Codex has posted (or a timeout is hit), then triages the findings instead of leaving the user to check back manually.
    0 installs
  2. ▌
    Pr Description Writer · osherboudara99
    PR Description Writer
    0 installs
  3. ▌
    Verify · osherboudara99
    Tests application code just written for bugs and confirms it actually fulfills the user's stated intent, by running it in an isolated sandboxed git worktree. Use when the user invokes /verify, or asks to "verify this works", "sandbox test this", "does this actually do what I wanted", or similar, after code has been written or changed. Spawns an isolated subagent that builds, lints, type-checks, tests, and actually runs/exercises the app, then cross-checks the result against the conversation's stated goals plus any spec/README/plan .md files in the repo.
    0 installs
  4. ▌
    Agents Md · osherboudara99
    Use when starting nontrivial work in a repo (read docs/AGENTS.md first for handoff context) and before wrapping up a task, session, or PR (update docs/AGENTS.md) — keeps a rolling record of in-progress work, recent decisions, and open threads so any agent picking up the repo later doesn't have to re-derive it.
    0 installs
  5. ▌
    Jev Review · osherboudara99 bundle
    Use when a code change is ready for review and you want an automated check that the diff actually matches the original request — surfaces unrelated changes, missing requirements, or security concerns before the assistant hands the work back, using TypeSafe's Jev judgment model.
    0 installs
  6. ▌
    Branch Naming · osherboudara99
    Governs how to name new git branches for this user, across every project on this machine. Use this whenever creating a new branch to start a feature, fix, refactor, or any other piece of dev work — branches must start with a conventional prefix followed by a short kebab-case summary of the change, instead of arbitrary or ticket-only names.
    0 installs
  7. ▌
    Pre Push Checklist · osherboudara99 bundle
    Governs what to check before running `git push` for this user, across every project on this machine. Use this every time you're about to push commits — run the repo's linter, type checker, and tests first, and block the push (asking the user to fix or confirm) if any of them fail, instead of pushing broken code straight through.
    0 installs
  8. ▌
    Incremental Commits · osherboudara99
    Governs how to commit work when doing software development with this user, across every project on this machine. Use this whenever writing code, implementing a feature, fixing a bug, or making any multi-step change in a git repository — commit in small, logical, step-by-step increments with conventional-commit prefixes instead of batching everything into one big commit at the end. Always consult this before staging/committing changes during development work, even if the user didn't explicitly ask for a commit at that moment.
    0 installs