AAWEA.ORG

Dependency Audit Weekly

Weekly loop to check outdated dependencies, propose safe upgrades, and open a summary.

👁 1,712 views 📥 1,160 installs 👤 by loops!

Manual start

↓

1

List outdated packages

Run npm outdated and summarize major vs patch updates.

> npm outdated || true
2

Propose upgrades

Recommend safe upgrades. Flag breaking changes and required code changes.

↓

✓

Exit condition: manual

Weekly audit summary delivered

📊 Flow Diagram

flowchart TD Start(["Interval start"]) Start --> S0 S0("List outdated packages") S1("Propose upgrades") S0 --> S1 Exit{"Weekly audit summary delivered"} S1 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "Dependency Audit Weekly" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

/loop 7d Start the "Dependency Audit Weekly" loop.

Goal: deliver a weekly dependency audit summary.
Between iterations run: npm outdated || true
Exit when: summary is posted with recommended upgrades.

Step 1: Run npm outdated, categorize updates, and propose a safe upgrade plan.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics