luoli523/harness-project-template

2Stars on the repository
13Mods indexed here, across every type
4mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

luoli523/harness-project-template

Skill Claude CodeCodex

Walks a diff across five axes — correctness, readability, architecture, security, performance — producing actionable review comments. Use before opening a PR for self-review, when reviewing someone else's PR, or any time a diff is larger than 10 LOC.

not rated 2 4mo ago A 55 tokens

luoli523/harness-project-template

Skill Claude CodeCodex

Enforces atomic commits on short-lived feature branches off main, with imperative commit messages that explain why, and rebase-based integration. Use when committing, branching, opening a PR, resolving merges, or structuring the final commit set before push.

not rated 2 4mo ago A 56 tokens

luoli523/harness-project-template

Skill Claude CodeCodex

Implements one thin vertical slice at a time — smallest change that leaves the system working, tested, and shippable. Use for every code change in this repo, no matter how small, after a task from the plan is selected.

not rated 2 4mo ago A 53 tokens

luoli523/harness-project-template

Skill Claude CodeCodex

Breaks an approved spec into ordered, verifiable tasks with acceptance criteria and ≤ 100 LOC diffs each. Use after a spec exists and before writing any implementation code, when scope is larger than a single file change, or when multiple people or agents might work in parallel.

not rated 2 4mo ago A 62 tokens

luoli523/harness-project-template

Skill Claude CodeCodex

Produces a structured feature specification before any code is written. Use when starting a new feature, when requirements are ambiguous or only exist as a rough idea, when a change will touch multiple modules, or when implementation would take more than 30 minutes.

not rated 2 4mo ago A 53 tokens

luoli523/harness-project-template

Skill Claude CodeCodex

Writes a failing test before the implementation and uses the Prove-It pattern for bug fixes. Use when adding any new business logic, when fixing any bug, or when changing an existing function's behavior.

not rated 2 4mo ago A 44 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: