Skip to content
TrustedSkillsbeta
Back to all skills

Laravel:Api Surface Evolution

Checked
jpcaparas·vlatest·backend·MIT

Analyzes Laravel API routes & controllers, identifying potential refactoring opportunities and evolution paths for improved maintainability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jpcaparas/superpowers-laravel --skill laravel:api-surface-evolution -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jpcaparas

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jpcaparas/superpowers-laravel at c5198b16cd.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c5198b16cd
Manifest
skills/api-surface-evolution/SKILL.md
Scanned
1 file, 30 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to understand and interact with Laravel API surface evolution. It facilitates the analysis of changes in API endpoints, request parameters, and response structures over time within a Laravel application. This capability is crucial for maintaining compatibility during updates and refactoring efforts.

When to use it

  • API Migration: When migrating an existing Laravel application to a new version or architecture, understand how APIs have changed.
  • Backward Compatibility Checks: Verify that recent API changes haven't broken older clients or integrations.
  • Documentation Updates: Automatically generate documentation reflecting the current state of your Laravel APIs.
  • Refactoring Analysis: Assess the impact of refactoring efforts on existing API consumers.

Key capabilities

  • Laravel API Surface Evolution analysis
  • Change tracking across API versions
  • Request parameter and response structure comparison

Example prompts

  • "Show me the differences in the /users endpoint between version 1.0 and 2.0."
  • "What request parameters were added or removed from the /products endpoint since last release?"
  • "Generate documentation for the current API surface of my Laravel application."

Tips & gotchas

This skill requires access to your Laravel application's codebase or deployment history. The accuracy of the analysis depends on consistent versioning and clear commit messages related to API changes.