agentsclimarketplace

Infra kit.workflow.review

Skill huyngopt1994/infras-kit/infras-kit-plugin/skills/infra-kit.workflow.review

Infras Kit Provide a Kit For All Infras Working

Install
npx -y skills add huyngopt1994/infras-kit --skill infra-kit.workflow.review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Make infra PRs reviewable: PR readiness checklist, traceability to ticket, and how to respond to review feedback.

SKILL.md

2.3 KB, as published. Nobody here has run it

Review Loop (PR Readiness + Feedback)

Use this skill when you are preparing to open a pull request, requesting review, or responding to review feedback for infra changes (Terraform/Helm/GitHub Actions/platform config).

Outcomes

  • Ensure the PR tells reviewers: what changed, why, risk, rollout/rollback, and verification evidence
  • Reduce back-and-forth by front-loading required context
  • Provide a consistent process for responding to feedback without losing traceability to the ticket

Where This Fits In The Flow

  • Use after infra-kit.workflow.verify and before merge.
  • Pair with infra-kit.workflow.audit for the cross-cutting safety gate.

Output Rules

  • Write PR-ready summary content into the work item:
    • docs/infras-kit/work-items/<id>-<slug>/confluence.md (can double as PR body)
    • and ensure implementation-notes.md contains verification evidence.

PR Readiness Checklist

Confirm:

  • The PR links to the ticket and matches the scope in ticket.md.
  • Acceptance criteria are testable and mapped to:
    • tasks (tasks.md)
    • verification evidence (implementation-notes.md or verification.md)
  • The PR description includes:
    • what changed and why
    • impact and risk
    • rollout steps
    • rollback steps and trigger
    • verification commands run + key results
  • Any required manual steps (GitHub UI settings, approvals, secrets) are called out explicitly.

Responding To Review Feedback

  1. Categorize feedback:
    • correctness/safety blockers
    • clarity/docs requests
    • style/nits
  2. For blockers, prioritize the smallest safe change and re-run verification.
  3. Update artifacts when needed:
    • if scope changes, update ticket.md / spec.md
    • if the plan changes, update plan.md and reflect it in tasks.md
  4. Record what changed in implementation-notes.md and add new evidence.
  5. When you disagree, propose an alternative with explicit trade-offs and a way to verify.

Guardrails

  • Do not merge with unresolved [NEEDS CLARIFICATION: ...] unless explicitly accepted as a spike with [ASSUMPTION: ...].
  • Do not answer reviewers with speculation; either cite evidence or propose a test.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.