Files
Opera-Extensions/opera-cache-cleaner-extension/AGENTS.md
ToxicCrzay270 8379c906c4
All checks were successful
Build / build (push) Successful in 8s
Release Dry Run / release-dry-run (push) Successful in 5s
Template Compliance / template-compliance (push) Successful in 4s
Repository Cleanup / cleanup-report (push) Successful in 4s
Security Scan / security-scan (push) Successful in 5s
Apply updated Codex repository kit guidance
2026-05-15 01:00:31 +02:00

1.6 KiB

Agent Instructions

Project

Opera Cache Cleaner is an Opera-compatible Chromium extension that clears only the browser cache for a selected time range and can optionally schedule repeated cache cleanup.

Repository Rules

  • Derive the repository owner and repository name from the target repository remote or CI repository context. Never reuse the owner from the repository kit remote.
  • Preserve the plain Manifest V3 extension structure. Do not add a framework unless the user explicitly asks for it.
  • Keep runtime code in background.js and popup/.
  • Keep permissions minimal. The extension currently uses only browsingData, storage, and alarms.
  • Do not add host permissions, network calls, cookie/history access, or broad browser permissions without documenting the reason.
  • Do not create a release unless the user explicitly asks for one.
  • Keep .codex/project.md aligned when commands, artifact paths, or release rules change.

Commands

Use these commands from this extension directory:

node --check background.js
node --check popup/popup.js
mkdir -p dist && zip -r dist/opera-cache-cleaner-extension.zip manifest.json background.js popup icons -x "*.DS_Store"

There is no package manager, dependency install, lint, or dependency audit command for the current project.

Artifacts

Expected release artifact from this extension directory:

dist/opera-cache-cleaner-extension.zip

Finish Checklist

  • git diff --check passes when the project is inside a Git repository.
  • node --check background.js passes.
  • node --check popup/popup.js passes.
  • Release documentation is updated when release behavior changes.