Files

Defame1297 044b2d3f08 fix(kyberforge): fix HOME/git scope-walkup false-FAILs in agent-audit

validate.sh's detect_scope() and validate-provenance.sh's
find_plugin_root() disagreed with new-agent.sh's already-correct,
documented walk-up semantics on three points, each causing validate.sh
to false-FAIL a legitimately-scaffolded project-scope agent pair:

- a marker-less directory walked up into $HOME (no .git/apm.yml of its
  own) was classified as user scope instead of project scope
- the .git-boundary branch returned the walked-to .git location instead
  of the conventional scope root, breaking any <root> that is a
  subdirectory of a larger git-tracked tree (monorepo package dirs)
- the new conventional-root arithmetic introduced to fix the above two
  cases had no guard against non-conventional/hand-placed file paths,
  which could point it at the wrong ancestor

Also adds scripts/check-scope-walkup-sync.sh, a behavioral drift-guard
(per ADR-0014's no-cross-skill-path precedent) that cross-checks the
four independently hand-ported walk-up implementations (validate.sh,
validate-provenance.sh, new-agent.sh, new-skill.sh) against real
fixture scaffolds, wired into .pre-commit-config.yaml at pre-push so
future drift between the ports is caught automatically.

Verified via bash tests/run-tests.sh (13/13) and targeted before/after
reproduction of each bug this closes.

2026-08-12 11:35:23 +00:00

README.md

feat(kyberforge): add agent-audit skill (closes #11 )

2026-07-04 10:06:37 +00:00

vale-wrap.sh

refactor(kyberforge): consolidate vale-wrap.sh's config parsing and subprocess spawns

2026-08-09 20:14:23 +00:00

validate-provenance.sh

fix(kyberforge): fix HOME/git scope-walkup false-FAILs in agent-audit

2026-08-12 11:35:23 +00:00

validate.sh

fix(kyberforge): fix HOME/git scope-walkup false-FAILs in agent-audit

2026-08-12 11:35:23 +00:00

README.md

scripts/

Executable code bundled with this skill. Agents run scripts in this directory to perform repeatable operations rather than reinventing the logic each run.

When to add a script

Add a script when agents independently reinvent the same logic across runs — building the same parser, chart, or validation routine from scratch each time. Bundle it here once, tested and reliable.

Script requirements (agentskills.io)

Scripts must be designed for non-interactive, agentic execution:

No interactive prompts — agents run in non-interactive shells. Accept all input via flags, env vars, or stdin. A script that blocks on TTY input hangs indefinitely.
Expose --help — this is how agents learn your script's interface. Keep the output concise; it enters the agent's context window.
Structured output — write data (JSON, CSV, TSV) to stdout. Write progress, warnings, and diagnostics to stderr.
Idempotent — prefer "create if not exists" over "create and fail on duplicate". Agents may retry on failure.
Meaningful exit codes — 0 for success, non-zero for failure. Use distinct codes for different failure types; document them in --help.
Dry-run support — add --dry-run for destructive operations.

Self-contained scripts

Bundle dependencies inline so the agent can run the script with a single command.

Python (PEP 723 + uv):

# /// script
# dependencies = ["requests>=2.31,<3"]
# requires-python = ">=3.11"
# ///
import requests

uv run scripts/my-script.py

If no scripts are needed

Delete this README and the scripts/ directory entirely.