[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0C8KTXWQ463FR653N783M":3,"skill-same:01M7F0C8KTXWQ463FR653N783M":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F0C8KTXWQ463FR653N783M","coding-like-redd",null,"Redd's Python and Rust coding standards -- tooling (uv\u002Fruff\u002Fty; cargo\u002Fclippy\u002Fnextest), code style rules, error\u002Flogging\u002Fsubprocess conventions, and required-project-file templates (including Makefiles). Load whenever writing, reviewing, editing, or scaffolding Python or Rust code, or asked about Redd's coding standards, in ANY project.","nredd\u002Fpi-harness","nredd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13305966?v=4","01M7F0BM37W1RA8H414NPR8DA2","Nicholas Redd","01M7F0BM3WAMMSDBJPB1AM308V",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fcoding-like-redd\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: coding-like-redd\ndescription: Redd's Python and Rust coding standards -- tooling (uv\u002Fruff\u002Fty; cargo\u002Fclippy\u002Fnextest), code style rules, error\u002Flogging\u002Fsubprocess conventions, and required-project-file templates (including Makefiles). Load whenever writing, reviewing, editing, or scaffolding Python or Rust code, or asked about Redd's coding standards, in ANY project.\n---\n\n## Python Development\n\n### Tooling (Astral Ecosystem)\n- **Package Manager**: `uv` for all dependency management\n- **Virtual Environments**: Use them!\n- **Formatting & Linting**: `ruff` -- single tool for both\n- **Type Checking**: `ty`. Not mypy, not pyright\n- **Testing**: `pytest` with comprehensive coverage\n- **Matrix Testing**: `tox`, configured in `[tool.tox]` inside `pyproject.toml`\n\n### Code Standards\n- PEP 604 unions only: `str | None`, `list[str]`, `dict[str, Any]`. Never `Optional[]`,\n  `Union[]`, `typing.List` -- including inside docstrings, which drift because nothing\n  enforces agreement with the signature\n- `from __future__ import annotations` at the top of every new module\n- Annotate every return, including `-> None`\n- Follow PEP 8 strictly\n- Module order: docstring, `__future__`, stdlib, third-party, first-party,\n  `LOGGER = logging.getLogger(__name__)`, compiled regex and SCREAMING constants, code\n- Module docstrings carry a `References:` list of links to whatever upstream tool or spec\n  the module models\n- Docstrings use my form, not Google or NumPy: `Parameters:` \u002F `Returns:` \u002F `Raises:`,\n  repeating types even though they are annotated. Private helpers get docstrings too.\n  Pydantic models do not -- `description=` on the field is the doc\n- Imports at module top. The only two acceptable local imports are breaking a cycle and\n  deferring genuine import cost. Comment which one it is\n- Compile regex once at module level, `SCREAMING_CASE`. Never `re.compile` in a loop\n- `pathlib` only. `Path(str(x)).resolve()`, then check `.exists()` \u002F `.is_file()`\n- Pick the container deliberately: Pydantic `BaseModel` for validated or serialized data,\n  `TypedDict` for a function's return shape, `@dataclass(frozen=True)` for internal\n  holders, `StrEnum` for closed string sets\n- `dict` merge with `|` and `|=`, never `.update()` in an expression. Order-preserving\n  dedup is `list(dict.fromkeys(...))`\n- `TODO(redd):` and `NOTE(redd):` are the only marker forms. No FIXME, HACK, or XXX, no\n  bare `TODO`. A bare issue URL as the body is fine, so is candid self-criticism\n- My abbreviations: `cfg` (never `config`), `ti`, `ws`, `env`, `opts`, `cmd`\n\n### Never Waive, Fix\n- Never add `# noqa` or `# type: ignore`. I configure both to be ignored outright\n  (`ruff check --fix --ignore-noqa`, ty `respect-type-ignore-comments = false`). Fix the\n  source. If a rule is genuinely wrong, change the config and say so\n- Never widen an exclude or ignore list to make a check pass. Tighten the gate, then fix\n  the code to clear it\n- Every lint exception carries a written reason for why it exists\n\n### Errors, Logging, Validation\n- Guard clauses open every function. Validate, coerce, then re-validate\n- Backtick identifiers inside message strings. Single-quote interpolated VALUES so an\n  empty string is visible: `f\"Path does not exist: '{source_path}'\"`\n- Exception choice is semantic, respect it. `ValueError` \u002F `TypeError` \u002F\n  `FileNotFoundError` mean bad input and the caller is at fault. Domain-retryable and\n  domain-fatal failures get distinct types. Never `raise Exception` in new code\n- Wrap and re-raise with `from e`. The new message names the operation and interpolates\n  the original\n- Module-level `LOGGER`, never `print`. **f-strings in log calls are the house style --\n  do not \"fix\" them to `%s` lazy formatting.** Use levels with intent\n- Validate before expensive work starts, not after\n\n### Shell-out and Subprocess\n- Logic goes in Python, never in the shell string. Evaluate every conditional, loop,\n  retry, and parse in Python and interpolate the result:\n  `{\"set -e\" if self.exit_on_error else \"\"}`. No branching inside embedded shell\n- Build args as `list[str]` and join at the very end with `shlex.join`. `shlex.quote`\n  anything interpolated. Optional flags via `*([flag] if cond else [])` so the command\n  stays one expression\n- `textwrap.dedent` for any embedded script block\n- Absolute binary paths always (`\u002Fusr\u002Fbin\u002Ffind -O3`). `$PATH` is not trusted\n- `subprocess.check_output(..., text=True, stderr=subprocess.STDOUT)`, list-form args.\n  `shell=True` only for a genuine pipeline\n\n### Required Project Files\n1. **pyproject.toml** -- comprehensive, including `[tool.ruff]`, `[tool.ty]`, `[tool.tox]`\n2. **README.md** -- kept current with installation, usage, examples\n3. **Makefile** -- developer convenience commands (template below)\n4. **tests\u002F** -- unit tests with real coverage\n\n`src\u002F` layout is right for a distributable library. A flat package layout is fine for\napplications and DAG or automation repos. Do not impose `src\u002F` where it buys nothing.\n\n### Makefile Template for Python\n```makefile\n.PHONY: help install format lint type test tox clean all\n\nhelp:\n\t@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = \":.*?## \"}; {printf \"\\033[36m%-20s\\033[0m %s\\n\", $$1, $$2}'\n\ninstall:  ## Install dependencies with uv\n\tuv sync --all-extras\n\nformat:  ## Format code with ruff\n\tuv run ruff format .\n\nlint:  ## Lint code with ruff\n\tuv run ruff check . --fix --ignore-noqa\n\ntype:  ## Type check with ty\n\tuv run ty check\n\ntest:  ## Run tests with pytest\n\tuv run pytest -v --cov=src --cov-report=term-missing\n\ntox:  ## Run matrix tests\n\tuv run tox\n\nclean:  ## Clean artifacts\n\trm -rf .pytest_cache .ruff_cache .tox dist build *.egg-info\n\tfind . -type d -name __pycache__ -exec rm -rf {} +\n\nall: format lint type test  ## Run full CI pipeline\n```\n\n## Rust Development\n\n### Tooling\n- **Formatter**: `rustfmt` with rustfmt.toml config\n- **Linter**: `clippy` at pedantic level\n- **Testing**: `cargo test` and `cargo nextest` (preferred)\n- **Documentation**: `cargo doc` must build without warnings\n- **Additional Tools**: cargo-deny, cargo-outdated\n\n### Code Standards\n- Follow Rust idioms and conventions religiously\n- Leverage the type system fully\n- Modern patterns (async\u002Fawait, Result\u002FOption)\n- Zero-cost abstractions\n- Comprehensive documentation comments (`\u002F\u002F\u002F` and `\u002F\u002F!`)\n- Proper error handling, avoid unwrap\u002Fexpect in production\n\n### Required Project Files\n1. **Cargo.toml** -- complete project configuration\n2. **README.md** -- kept current\n3. **Makefile** -- developer convenience commands (template below)\n4. **rustfmt.toml** -- formatting configuration\n5. **tests\u002F** -- integration tests\n6. **examples\u002F** -- usage examples\n7. **benches\u002F** -- benchmarks for performance-critical code\n\n### Makefile Template for Rust\n```makefile\n.PHONY: help build test fmt lint doc check clean all\n\nhelp:\n\t@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = \":.*?## \"}; {printf \"\\033[36m%-20s\\033[0m %s\\n\", $$1, $$2}'\n\nbuild:  ## Build the project\n\tcargo build\n\ntest:  ## Run tests\n\tcargo test --all-features\n\nfmt:  ## Format code\n\tcargo fmt --all\n\nlint:  ## Run clippy\n\tcargo clippy --all-targets --all-features -- -W clippy::pedantic\n\ndoc:  ## Build documentation\n\tcargo doc --no-deps --all-features\n\ncheck:  ## Fast compile check\n\tcargo check --all-targets --all-features\n\nclean:  ## Clean artifacts\n\tcargo clean\n\nall: fmt lint check test doc  ## Run full CI\n```\n","## Python Development\n\n### Tooling (Astral Ecosystem)\n- **Package Manager**: `uv` for all dependency management\n- **Virtual Environments**: Use them!\n- **Formatting & Linting**: `ruff` -- single tool for both\n- **Type Checking**: `ty`. Not mypy, not pyright\n- **Testing**: `pytest` with comprehensive coverage\n- **Matrix Testing**: `tox`, configured in `[tool.tox]` inside `pyproject.toml`\n\n### Code Standards\n- PEP 604 unions only: `str | None`, `list[str]`, `dict[str, Any]`. Never `Optional[]`,\n  `Union[]`, `typing.List` -- including inside docstrings, which drift because nothing\n  enforces agreement with the signature\n- `from __future__ import annotations` at the top of every new module\n- Annotate every return, including `-> None`\n- Follow PEP 8 strictly\n- Module order: docstring, `__future__`, stdlib, third-party, first-party,\n  `LOGGER = logging.getLogger(__name__)`, compiled regex and SCREAMING constants, code\n- Module docstrings carry a `References:` list of links to whatever upstream tool or spec\n  the module models\n- Docstrings use my form, not Google or NumPy: `Parameters:` \u002F `Returns:` \u002F `Raises:`,\n  repeating types even though they are annotated. Private helpers get docstrings too.\n  Pydantic models do not -- `description=` on the field is the doc\n- Imports at module top. The only two acceptable local imports are breaking a cycle and\n  deferring genuine import cost. Comment which one it is\n- Compile regex once at module level, `SCREAMING_CASE`. Never `re.compile` in a loop\n- `pathlib` only. `Path(str(x)).resolve()`, then check `.exists()` \u002F `.is_file()`\n- Pick the container deliberately: Pydantic `BaseModel` for validated or serialized data,\n  `TypedDict` for a function's return shape, `@dataclass(frozen=True)` for internal\n  holders, `StrEnum` for closed string sets\n- `dict` merge with `|` and `|=`, never `.update()` in an expression. Order-preserving\n  dedup is `list(dict.fromkeys(...))`\n- `TODO(redd):` and `NOTE(redd):` are the only marker forms. No FIXME, HACK, or XXX, no\n  bare `TODO`. A bare issue URL as the body is fine, so is candid self-criticism\n- My abbreviations: `cfg` (never `config`), `ti`, `ws`, `env`, `opts`, `cmd`\n\n### Never Waive, Fix\n- Never add `# noqa` or `# type: ignore`. I configure both to be ignored outright\n  (`ruff check --fix --ignore-noqa`, ty `respect-type-ignore-comments = false`). Fix the\n  source. If a rule is genuinely wrong, change the config and say so\n- Never widen an exclude or ignore list to make a check pass. Tighten the gate, then fix\n  the code to clear it\n- Every lint exception carries a written reason for why it exists\n\n### Errors, Logging, Validation\n- Guard clauses open every function. Validate, coerce, then re-validate\n- Backtick identifiers inside message strings. Single-quote interpolated VALUES so an\n  empty string is visible: `f\"Path does not exist: '{source_path}'\"`\n- Exception choice is semantic, respect it. `ValueError` \u002F `TypeError` \u002F\n  `FileNotFoundError` mean bad input and the caller is at fault. Domain-retryable and\n  domain-fatal failures get distinct types. Never `raise Exception` in new code\n- Wrap and re-raise with `from e`. The new message names the operation and interpolates\n  the original\n- Module-level `LOGGER`, never `print`. **f-strings in log calls are the house style --\n  do not \"fix\" them to `%s` lazy formatting.** Use levels with intent\n- Validate before expensive work starts, not after\n\n### Shell-out and Subprocess\n- Logic goes in Python, never in the shell string. Evaluate every conditional, loop,\n  retry, and parse in Python and interpolate the result:\n  `{\"set -e\" if self.exit_on_error else \"\"}`. No branching inside embedded shell\n- Build args as `list[str]` and join at the very end with `shlex.join`. `shlex.quote`\n  anything interpolated. Optional flags via `*([flag] if cond else [])` so the command\n  stays one expression\n- `textwrap.dedent` for any embedded script block\n- Absolute binary paths always (`\u002Fusr\u002Fbin\u002Ffind -O3`). `$PATH` is not trusted\n- `subprocess.check_output(..., text=True, stderr=subprocess.STDOUT)`, list-form args.\n  `shell=True` only for a genuine pipeline\n\n### Required Project Files\n1. **pyproject.toml** -- comprehensive, including `[tool.ruff]`, `[tool.ty]`, `[tool.tox]`\n2. **README.md** -- kept current with installation, usage, examples\n3. **Makefile** -- developer convenience commands (template below)\n4. **tests\u002F** -- unit tests with real coverage\n\n`src\u002F` layout is right for a distributable library. A flat package layout is fine for\napplications and DAG or automation repos. Do not impose `src\u002F` where it buys nothing.\n\n### Makefile Template for Python\n```makefile\n.PHONY: help install format lint type test tox clean all\n\nhelp:\n\t@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = \":.*?## \"}; {printf \"\\033[36m%-20s\\033[0m %s\\n\", $$1, $$2}'\n\ninstall:  ## Install dependencies with uv\n\tuv sync --all-extras\n\nformat:  ## Format code with ruff\n\tuv run ruff format .\n\nlint:  ## Lint code with ruff\n\tuv run ruff check . --fix --ignore-noqa\n\ntype:  ## Type check with ty\n\tuv run ty check\n\ntest:  ## Run tests with pytest\n\tuv run pytest -v --cov=src --cov-report=term-missing\n\ntox:  ## Run matrix tests\n\tuv run tox\n\nclean:  ## Clean artifacts\n\trm -rf .pytest_cache .ruff_cache .tox dist build *.egg-info\n\tfind . -type d -name __pycache__ -exec rm -rf {} +\n\nall: format lint type test  ## Run full CI pipeline\n```\n\n## Rust Development\n\n### Tooling\n- **Formatter**: `rustfmt` with rustfmt.toml config\n- **Linter**: `clippy` at pedantic level\n- **Testing**: `cargo test` and `cargo nextest` (preferred)\n- **Documentation**: `cargo doc` must build without warnings\n- **Additional Tools**: cargo-deny, cargo-outdated\n\n### Code Standards\n- Follow Rust idioms and conventions religiously\n- Leverage the type system fully\n- Modern patterns (async\u002Fawait, Result\u002FOption)\n- Zero-cost abstractions\n- Comprehensive documentation comments (`\u002F\u002F\u002F` and `\u002F\u002F!`)\n- Proper error handling, avoid unwrap\u002Fexpect in production\n\n### Required Project Files\n1. **Cargo.toml** -- complete project configuration\n2. **README.md** -- kept current\n3. **Makefile** -- developer convenience commands (template below)\n4. **rustfmt.toml** -- formatting configuration\n5. **tests\u002F** -- integration tests\n6. **examples\u002F** -- usage examples\n7. **benches\u002F** -- benchmarks for performance-critical code\n\n### Makefile Template for Rust\n```makefile\n.PHONY: help build test fmt lint doc check clean all\n\nhelp:\n\t@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = \":.*?## \"}; {printf \"\\033[36m%-20s\\033[0m %s\\n\", $$1, $$2}'\n\nbuild:  ## Build the project\n\tcargo build\n\ntest:  ## Run tests\n\tcargo test --all-features\n\nfmt:  ## Format code\n\tcargo fmt --all\n\nlint:  ## Run clippy\n\tcargo clippy --all-targets --all-features -- -W clippy::pedantic\n\ndoc:  ## Build documentation\n\tcargo doc --no-deps --all-features\n\ncheck:  ## Fast compile check\n\tcargo check --all-targets --all-features\n\nclean:  ## Clean artifacts\n\tcargo clean\n\nall: fmt lint check test doc  ## Run full CI\n```\n",{"name":5,"description":7},"main","9ca373de7213ce33ac1c383b5706b72feb82bac9","packages\u002Fpreset\u002Fskills\u002Fcoding-like-redd",1,"https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness","https:\u002F\u002Fgithub.com\u002Fnredd","DV Infra & Methodology @ QCOM | Caltech '19","2026-11-15 12:27:17",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add nredd\u002Fpi-harness --skill coding-like-redd",{"tool":38,"command":39},"bunx","bunx skills add nredd\u002Fpi-harness --skill coding-like-redd",{"tool":41,"command":42},"pnpm","pnpm dlx skills add nredd\u002Fpi-harness --skill coding-like-redd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fcoding-like-redd\u002FSKILL.md",true,[],[47,54,61],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F0CJ09TSN5H7H6QWHVYFJG","ship-issue","Address a GitHub issue in a dedicated git worktree -- implement, gate, obtain exact-HEAD reviews, open a PR, and hand protected merge ownership to the parent. Use when the user names an issue URL or number and wants it shipped.","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fship-issue\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F0CCGWM47A2796Q6FH8AV8","get-it-merged","Land a requested set of open PRs as a dependency-aware merge train: the parent reviews, arms protected auto-merge, watches each terminal outcome with a native monitor, and advances until the list is merged or genuinely blocked. Use when multiple PRs are open in one repo and the user wants them merged.","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fget-it-merged\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F0C3AZT3FSYY70WBHJZZD9","code-review","Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue\u002Fspec asked for?). Runs both reviews in parallel read-only `code-reviewer` sub-agents through the configured review route and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","https:\u002F\u002Fgithub.com\u002Fnredd\u002Fpi-harness\u002Fblob\u002Fmain\u002Fpackages\u002Fpreset\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[]]