Is create-removal-issue safe to install?

SaferSkills independently audited create-removal-issue (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/prestashop-module-development/ps9-core-ai/Component/Migration/skills/create-removal-issue/SKILL.md · 1 file

skills/prestashop-module-development/ps9-core-ai/Component/Migration/skills/create-removal-issue/SKILL.md1.8 KB · Markdown

name: create-removal-issue

description: >

Create a GitHub issue that targets the actual removal of the legacy controller

in the next major version. The issue tracks readiness prerequisites and

assigns a major release milestone.

produces: "GitHub issue tracking the actual removal of Admin{Domain}sController in the next major version"

create-removal-issue

Prerequisites (implicit)

The migrated Symfony page is GA (stability="stable", state=1) and has been stable for at least one minor release with no P1 regressions.

Instructions

Create a GitHub issue with title: Remove deprecated Admin{Domain}sController.
Body:

   **Target:** PS X.0

   **Context:** The new `{Domain}Controller` (Symfony) is GA since PS W.V (PR #YYYYY).

   **Prerequisites:**
   - [ ] GA page has been stable for ≥1 minor release with no P1 regressions
   - [ ] Migration guide published (release notes / dev blog)
   - [ ] All known modules updated (verify with ecosystem team)

   **Files to delete:**
   - `controllers/admin/Admin{Domain}sController.php`
   - Legacy-only service registrations referencing this controller

   **Files to update:**
   - Remove `_legacy_feature_flag: {domain}` from routing YAML once the flag entry itself is dropped
   - Clean up `feature_flag.xml` entry if no longer needed

Assign to the team's major release milestone.
Tag with: major-release, legacy-cleanup.

Rules

Conventions (timing, reference GA PR) are in Migration/CONTEXT.md. Skill-specific reminders:

The _legacy_controller: Admin{Domain}s attribute on routes is kept (preserves URL compatibility for legacy admin links) — do not list it as a "file to update"
Never create a PR for removal until all prerequisites in the issue are checked

create-removal-issue— agent skill

Is create-removal-issue safe to install?

create-removal-issue

Prerequisites (implicit)

Instructions

Rules

Audit the pieces. Scan the whole. Decide.