Skills software-engineer
📦

software-engineer

Content revision r1 Safe

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.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "software-engineer" from https://skillstore.io/skills/acskamloops-software-engineer.md and its manifest at https://skillstore.io/api/skills/acskamloops-software-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/acskamloops-software-engineer.md Signed manifest GET /api/skills/acskamloops-software-engineer/manifest Signed lockfile GET /api/skills/acskamloops-software-engineer/lockfile

Test it

Using "software-engineer". Add a validation check to a form handler.

Expected outcome:

The assistant identifies the existing validation pattern, applies a small handler update, and suggests the focused form test to run.

Using "software-engineer". Refactor a service method that has duplicated branching.

Expected outcome:

The assistant keeps behavior unchanged, extracts the repeated decision path, and recommends the existing service test suite for validation.

Using "software-engineer". Implement a vague performance improvement request.

Expected outcome:

The assistant asks for target metrics, affected workflows, and acceptable tradeoffs before proposing code changes.

Security Audit

Safe
v9 • 7/6/2026 Open versioned report

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.

1
Files scanned
13
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/acskamloops-software-engineer/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/acskamloops-software-engineer/security.svg)](https://skillstore.io/skills/acskamloops-software-engineer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/acskamloops-software-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/acskamloops-software-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/acskamloops-software-engineer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

ACSKamloops. (2026). software-engineer security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/acskamloops-software-engineer/audits/9

BibTeX citation

@techreport{acskamloops-acskamloops-software-engineer-2026, author = {ACSKamloops}, title = {software-engineer security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/acskamloops-software-engineer/audits/9}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "software-engineer security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "ACSKamloops" date-released: "2026-07-06" url: "https://skillstore.io/skills/acskamloops-software-engineer/audits/9" identifiers: - type: other value: "skillstore:acskamloops-software-engineer:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

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

Frequently Asked Questions

What does this skill help with?
It helps AI coding assistants make small, reviewable, and testable software changes.
Does it run commands automatically?
No. The skill is guidance text and does not include executable scripts.
Can it handle unclear requirements?
Yes. It tells the assistant to ask one to three clarifying questions when requirements are ambiguous.
Does it add new dependencies?
It guides the assistant to prefer existing repository patterns and utilities before adding dependencies.
Is it useful for code review?
Yes. Its focus on small diffs and validation steps supports practical review workflows.
Is it safe for community marketplace use?
The reviewed file contains no scripts, network calls, credential access, or prompt injection attempts.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/ACSKamloops/shs-engine/tree/master/.codex/skills/software-engineer

Ref

c1fdca50ff516318f65fed0d7f9e82797c5171dc

Maintenance freshness

7/18/2026

Usage

11 downloads · 184 views

File structure

📄 SKILL.md