一键在 Manus 中运行任何 Skill

lenslab-pr-readiness

星标0

分支0

更新时间2026年7月4日 00:15

Use before opening, updating, or merging a lenslab PR, especially after decode, core, dependency, binary-size, roadmap, or CLI-output changes. Checks roadmap freshness, crate boundaries, release-size impact, and PR verification evidence.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

attila

attila/lenslab

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Lenslab PR readiness

Run this before a PR is considered merge-ready.

Required checks

Roadmap freshness:
- Read docs/ROADMAP.md.
- Confirm the merged work is reflected under Done.
- Confirm Up Next names the next concrete task.
- Confirm deferred gaps are explicit.
Crate boundary:
- For decode/core changes, confirm LGPL-linked dependencies remain confined to lenslab-decode.
- Confirm lenslab-core stays dependency-free unless the PR intentionally changes that boundary.
- Useful checks:
  - cargo tree -p lenslab-core
  - rg "rawler|tiff" lenslab-core -n
Release binary size:
- For dependency, decode, CLI, or release-profile changes, build release and record the binary size.
- Useful checks:
  - cargo build --release -p lenslab-cli
  - ls -lh target/release/lenslab
- Treat unexpected growth as a design issue. Explain the reason or reduce it.
Output contract:
- For CLI output changes, verify machine-readable output stays on stdout and diagnostics stay on stderr.
Gates:
- Run just ci before claiming done.
- Run just test-fixtures after decode, fixture, or CI changes.
- For integration-test targets, use Cargo's target selector rather than a bare test-name filter, which can compile the integration test binary while running zero tests:
```
cargo test -p lenslab-cli --test analyse_cli
```

Reporting

Report the command and summary/exit line for every verification claim. For PRs, keep the body terse and include only the checks that explain risk.

同仓库更多 Skills

同仓库

lens-test

attila/lenslab

Interpret lenslab analyse JSON, relay only CLI-prescribed capture fixes, and keep the Rust CLI as the only measurement engine. Use when a user wants to assess a lens copy from DNG/TIFF captures, understand copy_assessment support, or get reshoot guidance.

2026-07-160

lens-test

attila/lenslab

Interpret lenslab analyse JSON and coach lens-copy capture reshoots using the shared lenslab skill core.

2026-07-160

post-work-compounding

attila/lenslab

Use after a larger piece of work or specialised targeted bugfix, before merge, to decide what should be compounded as a repo-local skill, a docs/solutions institutional learning, a rule update, or nothing. Start by showing candidates, then produce only the artefacts that earn their place.

2026-07-020

github-pr-ci-status

attila/lenslab

Use when checking whether GitHub Actions CI has run or passed on a pull request via the GitHub MCP tools (`mcp__github__pull_request_read`) — before claiming CI is green, red, or hasn't run yet.

2026-07-010

rustup-repair

attila/lenslab

Use when a rustup toolchain install is broken — `cargo`/`rustc` missing or failing to load (e.g. `librustc_driver-*` dylib/so not found), or `rustup toolchain install` reports "toolchain is already up to date" yet rustc errors. Repairs an interrupted toolchain install (common after a setup-script or container interruption).

2026-06-300

name	lenslab-pr-readiness
description	Use before opening, updating, or merging a lenslab PR, especially after decode, core, dependency, binary-size, roadmap, or CLI-output changes. Checks roadmap freshness, crate boundaries, release-size impact, and PR verification evidence.

Lenslab PR readiness

Run this before a PR is considered merge-ready.

Required checks

Roadmap freshness:
- Read docs/ROADMAP.md.
- Confirm the merged work is reflected under Done.
- Confirm Up Next names the next concrete task.
- Confirm deferred gaps are explicit.
Crate boundary:
- For decode/core changes, confirm LGPL-linked dependencies remain confined to lenslab-decode.
- Confirm lenslab-core stays dependency-free unless the PR intentionally changes that boundary.
- Useful checks:
  - cargo tree -p lenslab-core
  - rg "rawler|tiff" lenslab-core -n
Release binary size:
- For dependency, decode, CLI, or release-profile changes, build release and record the binary size.
- Useful checks:
  - cargo build --release -p lenslab-cli
  - ls -lh target/release/lenslab
- Treat unexpected growth as a design issue. Explain the reason or reduce it.
Output contract:
- For CLI output changes, verify machine-readable output stays on stdout and diagnostics stay on stderr.
Gates:
- Run just ci before claiming done.
- Run just test-fixtures after decode, fixture, or CI changes.
- For integration-test targets, use Cargo's target selector rather than a bare test-name filter, which can compile the integration test binary while running zero tests:
```
cargo test -p lenslab-cli --test analyse_cli
```

Reporting

Report the command and summary/exit line for every verification claim. For PRs, keep the body terse and include only the checks that explain risk.