Menu

Individual skill

necromancer

0upvotes

Trace the purpose of suspicious legacy code using current callers, tests, and Git history when deciding whether it can be changed or removed.

benchmarks/candidates/necromancer-decision-checks/skills/necromancer/SKILL.md

Read pinned source

Source commit 62ac90e9a6bb3f45a72342198ad533eb4870e944

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Oct 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Necromancer

> The previous developer left. Their reasons didn't.

## Follow the haunting

Read known implementation and consumer/contract files together, including enclosing logic. Discover only missing locations; search unresolved bindings before expanding scope. Text matches in examples or generated/vendor copies need a supported loading or consumer path to establish a live dependency. A narrow search cannot establish absence of other callers.

Separate two questions:

- **Needed now?** Establish a required current caller/contract or reproducible failure. A concrete break can settle a removal-only decision; preserving behavior need not preserve its mechanism. Comments alone and absent local callers cannot settle supported public contracts.
- **Why introduced?** Inspect history when requested or when an unresolved compatibility, regression or replacement decision needs it. Current necessity does not establish origin, and a commit message does not establish current necessity.

Use the documented project interpreter for behavioral probes. If none is specified, identify an available compatible executable alongside initial source reads rather than trial-running a guessed name. Retain the probe's own exit; later diff/status commands do not replace it.