Skip to content

aea-report-finalize: front-load aea-parse-tags check to Step 0 #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
larsvilhuber wants to merge 1 commit into
base: development
Choose a base branch
from
Open

aea-report-finalize: front-load aea-parse-tags check to Step 0 #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .claude/skills/aea-report-finalize/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,11 +59,21 @@ didn't independently check the RA's work.
REPO_ROOT=$(git rev-parse --show-toplevel)
cd "$REPO_ROOT"
ls -d [0-9]*/ 2>/dev/null # the openICPSR numbered deposit directory
command -v aea-parse-tags # the only tag-consolidation tool this skill uses (Step 4)
```

Confirm `REPLICATION.md` exists at `$REPO_ROOT`. If it doesn't, stop — this
isn't a replication-template repo, or you're in the wrong directory.

`aea-parse-tags` is the only consolidation tool this skill ever runs — there
is no fallback to a different tool name, and none should be invented. If
`command -v aea-parse-tags` finds nothing, don't go looking for an older or
differently-named script (e.g. `aeareq` — retired, see Restrictions) — that
means the environment is missing a dependency, not that a different tool
should be substituted. Stop and tell the user `aea-parse-tags` isn't
installed here, rather than treating its absence as a judgment call to
surface later at Step 4.

## Step 1 — Gate: is this already approved, and is a follow-up round underway?

```bash
Expand Down