- Home
- Skills
- Testing & Debugging
- Augnes Software Change Check
Augnes Software Change Check
An installer saying “complete” is only the start of checking whether the intended installation works.
Free
Works with the AI Agents you already use
Augnes Software Change Check
Example session with this skill installed
The installer says it completed. Verify that candidate 0.2 was installed into the requested selected_profile and that the other profile was left unchanged. Do not repair the installer while checking it; leave a reproducible result.
- Read your context and instructions
- Compiled the augnes software change
Summary
FAIL — the installer updated the wrong profile. It exited successfully and printed Install complete, but the requested profile remained at version 0.1. The other profile was unexpectedly updated to 0.2.
This is a deliberately faulty, developer-authored local fixture, not a customer incident or a defect in an Augnes installer. Its behavior was observed on 2026-11-09 KST with Linux x86_64 and Python 3.12.14. It is not a live Agensi execution or a comparison against an agent using ordinary tools without this Skill.
Observed results
| Check | Exit | Original stdout | Assessment |
|---|---|---|---|
| Selected profile before | 0 | {"version": "0.1", "ready": true} | Baseline |
| Other profile before | 0 | {"version": "0.1", "ready": true} | Baseline |
| Candidate directly | 0 | {"version": "0.2", "ready": true} | PASS |
| Installer | 0 | Install complete | Completion only |
| Requested profile after | 0 | {"version": "0.1", "ready": true} | FAIL: expected 0.2 |
| Other profile after | 0 | {"version": "0.2", "ready": true} | FAIL: expected unchanged |
Stderr was empty for every command. Both snapshot captures exited 0. Their comparison exited
1, the helper's documented difference status, and returned:
{"added": [], "changed": ["default_profile/status.py"], "equal": false, "removed": [], "scope": "selected-files-only"}
Diagnosis
The installer parses --profile but copies into the hardcoded default profile. The requested profile remains at 0.1 despite exit 0 and the completion message.
The installer and candidate bytes were unchanged across the check. Executing the installed status scripts establishes the version behavior; the snapshots identify which selected file changed. Hashes alone would not establish successful installation.
Reproduce the investigation
No account, network, third-party package or Augnes installation is needed.
In a new disposable directory, save and run the following as make_fixture.py. It creates subject/ and refuses an already existing subject directory. Both profiles start at 0.1; the candidate reports 0.2.
from pathlib import Path
root = Path("subject")
root.mkdir()
for name, version in (("candidate", "0.2"),
("selected_profile", "0.1"), ("default_profile", "0.1")):
folder = root / name
folder.mkdir()
(folder / "status.py").write_text(
'import json\nprint(json.dumps({"version": "' + version
+ '", "ready": True}))\n', encoding="utf-8")
(root / "install.py").write_text('''import argparse
from pathlib import Path
import shutil
parser = argparse.ArgumentParser()
parser.add_argument("--profile", required=True)
args = parser.parse_args()
root = Path(__file__).resolve().parent
shutil.copyfile(root / "candidate/status.py", root / "default_profile/status.py")
print("Install complete")
''', encoding="utf-8")
Use the Skill's scripts/snapshot_inputs.py unchanged as received.py in the disposable directory, outside subject/. Individual-file hosts fetch that file through their loader; directory users copy the exact helper bytes.
From this directory, run:
python3 -E -s -S -B make_fixture.py
python3 -E -s -S -B received.py snapshot subject install.py candidate/status.py selected_profile/status.py default_profile/status.py > before.json
python3 -E -s -S -B subject/selected_profile/status.py
python3 -E -s -S -B subject/default_profile/status.py
python3 -E -s -S -B subject/candidate/status.py
python3 -E -s -S -B subject/install.py --profile subject/selected_profile
python3 -E -s -S -B subject/selected_profile/status.py
python3 -E -s -S -B subject/default_profile/status.py
python3 -E -s -S -B received.py snapshot subject install.py candidate/status.py selected_profile/status.py default_profile/status.py > after.json
python3 -E -s -S -B received.py compare before.json after.json
Next action and limits
The installer owner should honor the requested destination, then repeat these checks in a fresh fixture. Do not treat the candidate's direct execution as proof that the selected profile was upgraded.
Live Agensi loading, real installed-product integration and other runtimes remain NOT_RUN.
After retaining any permitted evidence outside it, remove only the task-owned disposable directory, including received.py. The development replay removed its temporary directory; it changed no actual installed profile.
The repository's existing test command replays this published fixture and checks both status results and the ZIP-delivered helper's snapshot comparison:
python3 -E -s -S -B scripts/test-software-change-inputs.py
Connects securely to your tools. The creator never sees your data.
About this skill
An installer saying “complete” is only the start of checking whether the intended installation works. A script may also work in a checkout while its delivered copy is missing a dependency.
Augnes Software Change Check helps your coding agent investigate one concrete installation, package-delivery, dependency or version change. It identifies the actual source, delivered files and destination; chooses relevant existing checks; and records commands, observed results, unresolved limits and the next useful action. When input identity matters, a small optional Python helper captures and compares explicitly selected files.
Use it for an upgrade check, an installation into a selected profile, or a package that must run outside its original checkout. The result is a concise report another developer or agent can reproduce. A diagnosed incompatibility or a clear explanation of what could not run is also a useful result.
The helper does not test application behavior, and equal file hashes are not a compatibility certificate. The Skill uses your project's actual checks and does not require a new framework, server, Augnes project or migration.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 8 days ago
- Free with an Agensi account
- Software
- The target project's existing testorverification tools
- Optional
Python 3.9+
Permissions
Reads the project and artifact files selected for the task. Uses terminal commands to run authorized existing checks and writes task-owned temporary files, snapshots and reports. The optional Python helper reads explicitly selected files and prints JSON; it does not execute the software being checked or contact a service. The Skill itself requires no additional external account, browser access or environment-variable access. Any additional permissions needed by the target project's checks depend on that task and must be authorized separately.