devline

Use this agent for bugs, test failures, or unexpected behavior. Follows scientific debugging: reproduce, gather evidence, hypothesize, test, fix, verify. <example> Context: Tests failing user: "The auth tests are failing with a null pointer exception" assistant: "I'll use the debugger agent to investigate the null pointer exception." </example>

Final quality gate. Comprehensive review covering security, credentials, code quality, tech debt, conventions, plan compliance, and architecture. Runs on any completed implementation. <example> Context: All tasks implemented and reviewed user: "Everything is reviewed, do the final deep review" assistant: "I'll use the deep-review agent for the final quality review." </example>

Use this agent for complex dependency migrations that involve breaking changes, API refactoring, package renames, or behavioral differences. Unlike the dependency-patcher (simple version bumps), this agent researches migration guides, runs ecosystem migration tools (OpenRewrite, Rector, codemods), refactors application code, and ensures everything compiles and passes tests. Launched by the migrate skill — never invoked directly. <example> Context: Migrate skill dispatching a Spring Boot 2→3 migration user: "Migrate spring-boot from 2.7.18 to 3.2.x in /home/user/repos/my-api. Migration guide: [URL]. Known changes: javax→jakarta namespace, Spring Security config changes." assistant: "I'll use the dependency-migrator agent to execute the Spring Boot 3 migration with OpenRewrite recipes and manual code fixes." <commentary> Complex migration with namespace changes, config changes, and potential behavioral differences. Needs Opus-level reasoning. </commentary> </example> <example> Context: Migrate skill dispatching AWS SDK v1→v2 user: "Migrate aws-sdk-java from 1.x to 2.x in /home/user/repos/billing-service. Use the AWS SDK migration tool (OpenRewrite recipe)." assistant: "I'll use the dependency-migrator agent to run the AWS SDK migration tool and handle remaining manual changes." <commentary> Migration with dedicated tooling available. Agent runs the tool first, then handles what it can't automate. </commentary> </example>

Use this agent to patch dependencies in a single repository. It detects ecosystems, checks if dependencies are affected, updates versions, verifies the build/tests pass, and commits+pushes. Launched by cve-patcher, eol-fixer, or other dependency management skills — never invoked directly by the user. <example> Context: CVE patcher launching per-repo agents user: "Patch CVE-2024-38816 (spring-webmvc, Maven, fix: 6.1.13) in /home/user/repos/my-api" assistant: "I'll use the dependency-patcher agent to check and patch the Spring vulnerability in my-api." <commentary> CVE patcher researched the CVE and is now dispatching a patcher agent to handle one repo. </commentary> </example> <example> Context: EOL fixer launching per-repo agents user: "Update express from 4.18.2 to 4.19.0 (CVE-2024-XXXXX) in /home/user/repos/frontend-app" assistant: "I'll use the dependency-patcher agent to update express in frontend-app." <commentary> CVE patcher dispatching a simple version bump to a second repo in parallel. </commentary> </example>

Use this agent for build systems, CI/CD, Docker/containers, infrastructure as code, dev tooling, package management, or deployment. <example> Context: CI/CD work user: "Set up GitHub Actions for the new service" assistant: "I'll use the devops agent to configure the CI/CD pipeline." </example>

This skill should be used when the user asks to "brainstorm", "refine an idea", "flesh out a feature", "define requirements". Guides interactive refinement of rough ideas into concise, actionable feature specifications. Focuses on the "what" and architecture — never the "how".

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for "brand", "brand identity", "voice", "visual identity", "brand guidelines", "messaging framework", "brand consistency", branded content, tone of voice, marketing assets, brand compliance, style guides.

Patch CVE vulnerabilities across one or many repositories. Invoke with a list of CVEs and optionally specific repo names. Researches each CVE (affected package, ecosystem, versions), then launches dependency-patcher agents to update, verify, commit, and push. Use this skill whenever the user mentions CVEs, security vulnerabilities in dependencies, patching dependencies, or updating packages for security fixes — even if they don't say 'CVE' explicitly but reference a security advisory or vulnerable dependency.

This skill should be used when the user asks to "debug this", "fix this bug", "find the root cause", "investigate an error", "troubleshoot", "why is this failing", "trace the issue", or mentions errors, exceptions, stack traces, or unexpected behavior that needs investigation. Launches the debugger agent for systematic root cause analysis.

Final comprehensive pull request review — the last gate before merge. Checks security, credentials, code quality, tech debt, conventions, and plan compliance.

5 hooks across 3 events