iotkit-battle-tested-review

Reviews IoTKit pull requests and field reports against operational failure evidence.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/w-pinkietech/iotkit --skill iotkit-battle-tested-review-w-pinkietech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iotkit-battle-tested-review
Source: https://github.com/w-pinkietech/iotkit/tree/main/.agents/skills/iotkit-battle-tested-review
Command: npx skills add https://github.com/w-pinkietech/iotkit --skill iotkit-battle-tested-review-w-pinkietech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing IoTKit changes for operational failure risks is hard to do consistently, and field reports often go untriaged or get over-promoted into features. This Skill applies the battle-tested review perspective so pull requests are checked against known field failure evidence and field reports are converted into the smallest durable outcome. ## Core Features & Use Cases - Pull request review: Runs node scripts/battle-tested-review.mjs select --base <base-ref> to select relevant review questions, guards, and coverage gaps for a diff, with --concern filtering for cross-cutting risks. - Field report triage: Follows SECURITY.md and the field-report Issue form to separate reported facts from confirmed evidence, redact sensitive data, and reuse existing entries for the same failure. - Outcome promotion: Promotes the smallest durable result: a review question for credible unconfirmed risk, a focused regression test for reproducible behavior, or a runbook link for verified operations. - Use Case: When an IoTKit contributor opens a PR touching the MQTT outbox retry logic, run the selection script, review the diff against the selected BT-NNN entries, and record the IDs or a reason for none. ## Quick Start Ask the assistant to review this IoTKit pull request against relevant field failure evidence using the battle-tested review perspective.

Frequently Asked Questions about iotkit-battle-tested-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an IoTKit pull request for operational failure risks?▼

Run node scripts/battle-tested-review.mjs select --base <base-ref> from the repo root to select relevant review questions, guards, and coverage gaps. Review the diff against the selections and record the selected BT-NNN IDs or a reason for none.

How do I triage an IoTKit field report?▼

Follow SECURITY.md, the field-report Issue form, and review/battle-tested/README.md. Redact before copying, separate reported facts from confirmed evidence, and reuse an existing entry when the same failure has already been recorded.

When should a field report become a regression test versus a review question?▼

Promote a focused regression test only for reproducible behavior, a review question for credible but unconfirmed risk, and a runbook link for verified operations. Never implement a feature solely from a hypothesis or a single report.

Does zero selections from the review script mean a change is safe?▼

No. Unmatched paths, concerns without entries, and zero selections are not proof of safety. The catalog is an index, not a safety verdict, and tests and runbooks remain authoritative.

What are the limitations of the battle-tested review catalog?▼

The catalog does not define the whole review process and is not a backlog or safety verdict. Start at review/README.md when choosing perspectives, and run focused tests only for the changed behavior rather than every catalog scenario.