skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
devsecops-inpt/deviceposture1 installs

software-engineering-code-review

Use for disciplined code reviews focused on correctness, maintainability, clarity, and regression risk.

How do I install this agent skill?

npx skills add https://github.com/devsecops-inpt/deviceposture --skill software-engineering-code-review
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    No security issues detected. This skill provides standard instructional guidelines for software engineering code reviews without any executable code, network access, or dangerous patterns.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Purpose

Provide a repeatable code-review workflow that catches defects early and improves long-term maintainability.

When to Use

  • Reviewing feature changes before merge.
  • Auditing risky refactors or bug fixes.
  • Evaluating pull requests with cross-module impact.

When Not to Use

  • Pure brainstorming with no code artifacts.
  • Trivial formatting-only edits with zero behavior impact.

Required Inputs

  • Changed files or pull request diff.
  • Relevant requirements and acceptance criteria.
  • Test results (if available).

Step-by-Step Workflow

  1. Read change intent and expected behavior first.
  2. Review correctness and edge-case handling.
  3. Review maintainability (naming, cohesion, duplication, complexity).
  4. Review safety (error handling, logging, input validation, authz where relevant).
  5. Verify test coverage for happy path, edge cases, and regressions.
  6. Summarize findings by severity and provide actionable fixes.

Expected Outputs

  • Prioritized findings with clear rationale.
  • Specific remediation suggestions.
  • Residual risk statement when verification is incomplete.

Failure and Edge-Case Handling

  • If requirements are unclear, list assumptions and mark confidence.
  • If tests are missing, explicitly flag verification gaps.
  • If context is partial, classify findings as best-effort and request missing artifacts.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/devsecops-inpt/deviceposture/software-engineering-code-review">View software-engineering-code-review on skillZs</a>