# Build Safer Code Changes

Software changes can become hard to review when scope grows or validation is unclear. This skill guides Claude, Codex, and Claude Code toward small patches, repo-aware decisions, and concrete checks.

## Install

```bash
npx skillstore add acskamloops/software-engineer
```

## Metadata

- Status: approved
- Slug: acskamloops-software-engineer
- Skillstore revision: r1
- Version status: missing
- Tree hash: 797752d27887d47f1228eca07b3104583a1c66d4a83c5d91ce20990be45d6a3c
- Author: ACSKamloops
- GitHub username: ACSKamloops
- License: MIT
- Repository: https://github.com/ACSKamloops/shs-engine/tree/master/.codex/skills/software-engineer
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/acskamloops-software-engineer
- Manifest: https://skillstore.pages.dev/api/skills/acskamloops-software-engineer/manifest

## Capabilities

- Encourages minimal, reviewable code patches.
- Prompts clarifying questions when requirements are ambiguous.
- Prioritizes existing repository patterns and utilities.
- Asks for validation steps when behavior changes.
- Discourages destructive actions without explicit user approval.

## Use Cases

- Refactor a Focused Module: Improve a small part of a codebase while preserving current behavior and keeping the diff reviewable.
- Implement a Clear Bug Fix: Turn a known defect into a scoped patch with an explicit validation command or test target.
- Review an Ambiguous Request: Identify missing requirements before implementation so the final change matches the project need.

## Prompt Templates

### Make a Small Change

```
Use the software-engineer skill. Make the smallest practical change for this request, follow existing repo patterns, and include one validation step.
```

### Fix a Bug Safely

```
Use the software-engineer skill. Investigate this bug, ask clarifying questions if needed, implement a narrow fix, and report how to verify it.
```

### Refactor Without Behavior Change

```
Use the software-engineer skill. Refactor this area without changing behavior, prefer existing utilities, and keep the diff easy to review.
```

### Plan and Validate a Risky Change

```
Use the software-engineer skill. First assess ambiguity and risk, then propose a compact implementation plan and validation strategy before editing files.
```

## Limitations

- Provides guidance only and does not include scripts or automation.
- Does not define language-specific coding standards.
- Requires access to the target repository for best results.
- Does not replace human review or project-specific tests.

## Best Practices

- Give the assistant a specific file, feature, or failing behavior.
- Share expected validation commands when the project already defines them.
- Review proposed destructive or broad changes before approving them.

## Anti Patterns

- Requesting a large rewrite without defining the target behavior.
- Skipping tests or validation after behavior changes.
- Adding new dependencies before checking existing project utilities.

## Security Audit

- Audited at: 2026-07-06T00:32:50.325\+00:00
- Summary: The single static finding is a false positive. SKILL.md line 11 tells the assistant to avoid destructive actions unless explicitly requested, which is a safety guardrail rather than reconnaissance or malware behavior.

## Stats

- Views: 184
- Downloads: 13
- Favorites: 0
- Popularity score: 0