jpeseWang

23 mods across 1 repository, 2 stars between them.

jpeseWang/solo-dev-workflow

Instructions file CodexOpenCode

Instructions for jpeseWang/solo-dev-workflow, covering solo dev workflow — agent guide, the workflow, code quality bar, correctness and design.

2 11d ago A 2,242 tokens original MIT

reviewer

02

jpeseWang/solo-dev-workflow

Agent

Read-only code reviewer with a fresh context. Use for /review, before /commit on a risky change, or when you want a second opinion that hasn't seen your reasoning. Returns concrete findings; never edits.

2 11d ago A 45 tokens original MIT

commit

03

jpeseWang/solo-dev-workflow

Command

A focused pipeline: understand the change, hold it to the four quality dimensions, fix the safe stuff, then commit with a clean message. No ceremony — no ticket lookup, no metrics.

2 11d ago A 0 tokens original MIT

debug

04

jpeseWang/solo-dev-workflow

Command

The rest of the workflow covers the happy path. This is for when something is broken, which is most days. It exists because debugging is where an assistant most reliably goes wrong: it reads the symptom, pattern-matches a plausible cause, changes something, and the symptom disappears for a reason nobody understands.

2 11d ago A 0 tokens original MIT

plan

05

jpeseWang/solo-dev-workflow

Command

Run this when you're starting anything non-trivial. The goal: leave with a clear, scoped plan, an entry in TASKS.md, and a feature branch — ready to code. Don't write the feature itself here; just set it up.

2 11d ago A 0 tokens original MIT

review

06

jpeseWang/solo-dev-workflow

Command

A second pair of eyes on the code you just wrote, before /commit. The risk in solo work is that nobody else ever reads the diff — this command is that reader. Output is a concrete findings list; you decide what to fix.

2 11d ago A 0 tokens original MIT

setup

07

jpeseWang/solo-dev-workflow

Command

Run this once, right after installing. Everything else in the workflow reads the Project context block — /test needs to know your test runner, /commit needs your lint command, /ship needs your base branch. Left blank, every command guesses, and a guess that's wrong is worse than a question.

2 11d ago A 0 tokens original MIT

ship

08

jpeseWang/solo-dev-workflow

Command

Even solo, a PR is worth it: it runs CI, gives a clean diff to skim before merging, and leaves a durable record. This uses the gh CLI.

2 11d ago A 0 tokens original MIT

test

09

jpeseWang/solo-dev-workflow

Command

Add the test that would have caught the bug, or that locks in the new behavior. Match the project's existing testing setup — don't introduce a new framework.

2 11d ago A 0 tokens original MIT

verify

10

jpeseWang/solo-dev-workflow

Command

/test proves the assertions you wrote are satisfied. This proves the software does what the task asked. They fail differently: a test suite can be entirely green while the button doesn't render, the endpoint 500s on the real payload, or the CLI prints the wrong thing.

2 11d ago A 0 tokens original MIT

wrap

11

jpeseWang/solo-dev-workflow

Command

The lightweight end-of-task ritual that replaces a ticket system. Leaves a durable trail in two committed files — no external service, no time accounting.

2 11d ago A 0 tokens original MIT

create-jira-task

14

jpeseWang/solo-dev-workflow

Command

You are an assistant that creates Jira tasks for the $PROJECTNAME project. Do NOT ask again for information the user has already provided.

2 11d ago A 0 tokens original MIT

daily-report

17

jpeseWang/solo-dev-workflow

Command

You are an assistant that creates a Daily Report in a text-ready format for the Acme project — suitable for the daily stand-up (16:00 Vietnam / 10:00 Portugal) and the Slack daily update.

2 11d ago A 0 tokens original MIT

logwork

18

jpeseWang/solo-dev-workflow

Command

You are the assistant that logs work to Jira for the PROJ tickets worked on during the day in the Acme project (single Jira project: PROJ at your-domain.atlassian.net).

2 11d ago A 0 tokens original MIT

push

19

jpeseWang/solo-dev-workflow

Command

Push code, automatically run /commit if not yet committed, compute elapsed time and log work to Jira accurately. Handles all edge cases: no-ticket, no-state, re-push, multi-task, duplicate worklog, corrupt state, negative elapsed, wrong commit author.

2 11d ago A 56 tokens original MIT

review-mine

20

jpeseWang/solo-dev-workflow

Command

You are a Senior Tech Lead reviewing uncommitted code for the $PROJECTNAME project. Review from 3 independent perspectives (Logic / Design / Security+UX). The output is a findings list for the user to decide what to fix.

2 11d ago A 0 tokens original MIT