Code Reviewer
CaoMeiYouRen/caomei-auth
审查当前 git 变更、PR、提交范围、技能定义文件、架构调整或安全敏感代码时使用。输出结构化 Review Gate 结论（Pass/Reject）、问题分级（blocker/warning/suggest）、最低验证矩阵、证据链与复查基线。覆盖正确性、安全、架构、SOLID、可删除代码、性能、异常处理与测试风险；默认只输出 review，不直接修改代码。用户提到 review、code…
Feature development workflow. An agent skill from sd0xdev/sd0x-harness.
Install Feature Dev
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sd0xdev/sd0x-harness feature-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/feature-dev .claude/skills/feature-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .claude/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sd0xdev/sd0x-harness feature-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/feature-dev .agents/skills/feature-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .agents/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sd0xdev/sd0x-harness feature-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/feature-dev .cursor/skills/feature-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .cursor/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/feature-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sd0xdev/sd0x-harness feature-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/feature-dev .gemini/skills/feature-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .gemini/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sd0xdev/sd0x-harness feature-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/feature-dev .github/skills/feature-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .github/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill feature-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sd0xdev/sd0x-harness feature-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/feature-dev .opencode/skills/feature-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-dev" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/feature-dev into .opencode/skills/feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
feature-dev- GitHub stars
- 192
- Token cost
- ~2.1k tokens
- SKILL.md length
- 746 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Feature development workflow. An agent skill from sd0xdev/sd0x-harness.
- Works in 3 steps: Run existing tests → Test adequacy review (mandatory for code… → Code review (auto-loop)
- : implementing features
- SKILL.md covers Trigger, When NOT to Use, Prohibited Actions and Workflow, plus 10 more sections
- Calls git and node
What it does
Feature Dev is an agent skill from sd0xdev/sd0x-harness. Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review and Human-in-the-loop approvals. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.
When your agent uses it
- : implementing features
- Running dev loop
Example prompts
- “/feature-dev”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Edit, Write, Bash, Skill, AskUserQuestion
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobEditWriteBashSkillAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Feature Dev loads about 2.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 746 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Glob, Edit, Write, Bash, Skill, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 746 words, ~2,110 tokens.
Download SKILL.mdSave it as
.claude/skills/feature-dev/SKILL.md (or your agent's skills folder).- name
- feature-dev
- description
- Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
- allowed-tools
- Read, Grep, Glob, Edit, Write, Bash, Skill, AskUserQuestion
Feature Development Skill
Trigger
- Keywords: develop feature, implement, write code, verify, precommit, refactor, simplify
When NOT to Use
- Just want to understand code (use Explore)
- Review code only (use codex-code-review)
- Review documents only (use doc-review)
- Pure test-only tasks without feature changes (use
/codex-test-reviewdirectly)
Prohibited Actions
❌ git add | git commit | git push — per @rules/git-workflow.mdThis skill implements features but does not commit. /precommit is a quality gate only. To commit, offer the menu per rules/git-workflow.md § Proactive Offer — a commit option on any real branch, a push option only where review-state.js offer allows one — and invoke /smart-commit --execute on selection; never print the command for the user to copy.
budget:token_budget200000</budget:token_budget>
Workflow
Requirements → Design → Implement → Test + Review → Precommit Gate → Doc Sync
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
/codex- /codex- /verify /precommit /update-docs
architect implement /codex-test-review (or /precommit) /create-request --update
/codex-review-fastLoad the intent first: identify the feature this work belongs to (from the task, the
spec/requirements being followed, or the paths being changed) and read
docs/features/<key>/intent-<key>.md if it exists — it overrides your default approach. Work
that contradicts one of its INV-* invariants or Non-goals stops and asks the user (cite the
line; amending intent is their re-decision). No identifiable feature → nothing to load; proceed.
Design before code: for a non-trivial change, briefly consider who owns each responsibility,
the simplest shape that fits the existing code, and why — and say what you chose when the choice
is non-obvious. Principles (clear names, small cohesive functions, dependency direction,
composition where it reduces coupling) are questions, not quotas: never add an abstraction to
demonstrate design. /codex-architect is for genuinely hard trade-offs (cross-module boundaries,
new public APIs, durable abstractions), not every feature.
agentctl (optional)
At the start, run node "${CLAUDE_PLUGIN_ROOT}/skills/agentctl-setup/scripts/agentctl-setup.js" status
once. Only when state is installed/enabled, offer to draft a task proposal from the ticket per
@skills/agentctl-setup/references/workflow-integration.md — the user accepts it with
/agentctl accept; any other state, say nothing about agentctl and continue. It is never a gate:
every review and precommit obligation in this skill is unchanged, and its evidence is context
beside a verdict, never the verdict.
Commands
| Phase | Command | Description |
|---|---|---|
| Design | /codex-architect | Get architecture advice |
| Implement | /codex-implement | Codex writes code |
| Test: Run | /verify | Run tests (lint → typecheck → unit → integration) |
| Test: Review | /codex-test-review | Mandatory — review test sufficiency (5 dimensions) |
| Test: Generate | /codex-test-gen | Generate unit tests for gaps |
| Test: Integration | /post-dev-test | Write missing integration/e2e tests |
| Review | /codex-review-fast | Code review (auto-loop) |
| Precommit | /precommit | lint + build + test (auto-loop canonical path) |
| Doc Sync | /update-docs | Sync docs with code |
| Doc Sync | /create-request --update | Update request progress |
| Refactor | /simplify | Final refactoring |
Test + Review Phase (Detail)
This is the core of feature-dev — ensuring sufficient test coverage before code review.
Step 1: Run existing tests
/verify → all tests pass?
Yes → Step 2
No → fix failures → re-run /verifyStep 2: Test adequacy review (mandatory for code changes)
/codex-test-review → ✅ Tests sufficient?
Yes → Step 3
No → close gaps (Step 2a) → /codex-test-review --continueStep 2a: Gap closure
| Gap Type | Remediation Command |
|---|---|
| Unit test missing/insufficient | /codex-test-gen → write tests → /verify |
| Integration/E2E missing | /post-dev-test → write tests → /verify |
Step 3: Code review (auto-loop)
/codex-review-fast → ✅ Ready?
Yes → Precommit Gate
No → fix issues → re-run /codex-review-fast (auto-loop)Show full SKILL.md (304 more words)Show less
Freshness rule
If code changes after the latest ✅ Tests sufficient gate (e.g., fixes from code review), rerun /verify then /codex-test-review --continue before proceeding to precommit gate.
Testing Requirements
Follow @rules/testing.md for conventions (AAA, naming, evidence model).
Follow @rules/testing-project.md for project-specific overrides (directories, runner, adequacy mode).
| Change Type | Test Requirements |
|---|---|
| New Service/Provider | Must have corresponding unit test |
| Modify existing logic | Existing tests pass + new logic tested |
| Bug fix | Must add regression test |
| New API endpoint | Integration test required |
| Cross-service change | E2E test required |
Test File Mapping
Use project convention from @rules/testing-project.md. If no override is defined, follow ecosystem defaults:
| Source Pattern | Test Pattern |
|---|---|
src/<module>/ | test/unit/<module>/ or test/<module>/ |
scripts/<name>.sh | test/scripts/<name>.test.js |
skills/<name>/SKILL.md | test/skills/<name>.test.js |
Output
- Implemented feature code + tests
- Test adequacy gate: ✅ Tests sufficient
- Review gate: ✅ Ready
- Precommit results: ✅ All Pass
Verification Checklist
- All tests pass (
/verify) - Test adequacy reviewed (
/codex-test-review) - Code review passed (
/codex-review-fast✅ Ready) - Precommit passed (
/precommit✅ All Pass) - No
git add/commit/pushexecuted
Doc Sync (after precommit Pass)
⚠️ Auto-triggered by @rules/auto-loop.md — behavior-layer rule, not hook-enforced.
Only when change maps to a feature under docs/features/. Target detection uses 3-level fallback — see /update-docs for algorithm details.
precommit Pass
→ Locate feature docs (see /update-docs 3-level fallback)
→ /update-docs docs/features/<feature>/2-tech-spec.md (current-authority doc)
→ /create-request --update docs/features/<feature>/requests/<date>-<title>.md (record: status + outcome only)
→ /codex-review-doc (ONE dispatch for every doc touched above)
→ Safety valve: new code diff? → back to review loop (see /update-docs)Sync the current-authority doc; append to the record. The tech spec states what is true now, so
code landing makes it stale and it is rewritten. A request ticket, review log or ADR states what was
decided or done at a point in time — it is updated with status and outcome, never rewritten to match
today's code, because rewriting it destroys the record. scripts/lib/doc-metadata.js decides which a
file is; /codex-review-doc reviews each under the profile that classification earns.
One /codex-review-doc for all of them, not one per file: the changed docs are a single review plan
(skills/doc-review/SKILL.md § Workflow). Per-file dispatch is what multiplied a three-file doc sync
into three whole-document reviews.
Review Loop
MUST re-review after fix until PASS (per @rules/auto-loop.md)
Review → Issues found → Fix → Re-review → ... → ✅ Pass → Next stepExamples
Input: Implement a fee calculation method
Action: /codex-architect → /codex-implement → /verify → /codex-test-review → /codex-review-fast → /precommitInput: This code needs refactoring
Action: /simplify → /verify → /codex-test-review → /codex-review-fast → /precommitInput: Feature dev, continue (resuming work)
Action: Check git status → identify remaining tasks → continue from current phase© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/feature-dev of sd0xdev/sd0x-harness.
Open the folder on GitHubat commit c9a2036
Compare with similar skills
Feature Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Dev this skillsd0xdev/sd0x-harness | 192 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Code ReviewerCaoMeiYouRen/caomei-auth | 220 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Plannotator Referencebacknotprop/plannotator | 9.2k | — | ~5.7k | Automated safety check: Warn | Apache-2.0 | |
| Code ReviewerMageByte-Zero/spec-superflow | 839 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Plannotator Reference
backnotprop/plannotator
Reference for picking the right Plannotator tool or command for plan review, code review, annotating files and URLs, archived plan decisions and Guided Reviews.
Code Reviewer
MageByte-Zero/spec-superflow
Review completed implementation batches for spec compliance and code quality.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
More from sd0xdev/sd0x-harness
All 91 skills in this repoAdr
sd0xdev/sd0x-harness
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…
Load PR Review
sd0xdev/sd0x-harness
Load GitHub PR review comments into AI session — analyze, triage, plan.
Next Step
sd0xdev/sd0x-harness
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.
Obsidian CLI
sd0xdev/sd0x-harness
Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.
Orchestrate
sd0xdev/sd0x-harness
Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.
PR Comment
sd0xdev/sd0x-harness
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.
Related
Categories
Questions about Feature Dev
What does Feature Dev do?
Feature development workflow. An agent skill from sd0xdev/sd0x-harness. Feature Dev is an agent skill from sd0xdev/sd0x-harness. Feature development workflow.
When should I use Feature Dev?
Feature Dev fits situations like: : implementing features; running dev loop.
How do I install Feature Dev in Claude Code?
Run `npx skills add sd0xdev/sd0x-harness --skill feature-dev -a claude-code`. Or copy the skill folder (skills/feature-dev in sd0xdev/sd0x-harness) into .claude/skills/feature-dev in your project. Claude Code loads it when a task matches its description.
How do I install Feature Dev in Codex?
Run `npx skills add sd0xdev/sd0x-harness --skill feature-dev -a codex`. Or copy the skill folder (skills/feature-dev in sd0xdev/sd0x-harness) into .agents/skills/feature-dev in your project. Codex loads it when a task matches its description.
Can I use Feature Dev in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill feature-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-dev, .gemini/skills/feature-dev, .github/skills/feature-dev and .opencode/skills/feature-dev in your project.
What does Feature Dev need to run?
Going by SKILL.md and its folder, Feature Dev needs the command-line tools its instructions call (git and node). Its frontmatter pre-approves these tools: Read, Grep, Glob, Edit, Write, Bash, Skill, AskUserQuestion.
Does Feature Dev access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Feature Dev safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Feature Dev use?
Feature Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Feature Dev use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Feature Dev?
Skills that share tags, products or a category with Feature Dev: Code Reviewer (CaoMeiYouRen/caomei-auth, 220 stars), Plannotator Reference (backnotprop/plannotator, 9.2k stars), Code Reviewer (MageByte-Zero/spec-superflow, 839 stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Feature Dev?
sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.
Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.