Skills develop-backend

📦

develop-backend

Name: develop-backend
Author: Crearize

Content revision r1 Safe ⚙️ External commands

Build Spring Boot Backend APIs

Backend changes can drift from project conventions, database docs, and test expectations. This skill gives a structured Spring Boot/MyBatis workflow from task intake through API, data, tests, and verification.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "develop-backend" from https://skillstore.io/skills/crearize-develop-backend.md and its manifest at https://skillstore.io/api/skills/crearize-develop-backend/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/crearize-develop-backend.md Signed manifest GET /api/skills/crearize-develop-backend/manifest Signed lockfile GET /api/skills/crearize-develop-backend/lockfile

Test it

Using "develop-backend". Add a user profile API with a new table.

Expected outcome:

A staged backend plan covering migration, DTOs, mapper, service, controller, OpenAPI, tests, and verification.
A completion checklist that includes branch checks, issue linkage, coverage, lint, server startup, and documentation updates.

Using "develop-backend". Refactor account service validation without changing API behavior.

Expected outcome:

A refactor approach that preserves controller contracts and moves business rules into the service layer.
A test plan for normal, boundary, and error cases with required Gradle verification.

Using "develop-backend". Prepare a backend task for handoff.

Expected outcome:

A concise handoff summary covering changed layers, test results, documentation updates, and server startup confirmation.

Security Audit

Safe

v10 • 7/9/2026 Open versioned report

Most static hits are Markdown backticks, inline file paths, or documentation snippets, so they are false positives. I confirmed the git pull and Gradle execution instructions because they can modify the workspace or execute project code. I found no prompt injection, credential collection, data exfiltration, or obfuscated payload in SKILL.md.

Files scanned

370

Lines analyzed

Review items

False positives ignored

Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:122-131

Ruby/shell backtick execution

```bash

This block tells the agent to run git pull origin main, which fetches remote content and can modify the working tree. It is legitimate development workflow but still requires user awareness.

Medium

SKILL.md:223-226

Ruby/shell backtick execution

```bash

This block instructs running ./gradlew check, which executes project build logic and tests from the repository. That is expected for backend verification but can execute untrusted code.

Medium

SKILL.md:243-246

Ruby/shell backtick execution

```bash

This block instructs running ./gradlew bootRun, which starts and executes the backend application. It is useful verification but can run arbitrary project code and services.

Medium

SKILL.md:284-310

Ruby/shell backtick execution

- [ ] `./gradlew bootRun` でサーバー起動成功

The completion checklist requires confirming ./gradlew bootRun succeeded, reinforcing application execution as part of normal use. The risk is execution of project code, not command injection.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/crearize-develop-backend/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/crearize-develop-backend/security.svg)](https://skillstore.io/skills/crearize-develop-backend?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/crearize-develop-backend?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-develop-backend/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/crearize-develop-backend.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Crearize. (2026). develop-backend security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-develop-backend/audits/10

BibTeX citation

@techreport{crearize-crearize-develop-backend-2026,
  author = {Crearize},
  title = {develop-backend security audit report (audit version 10)},
  institution = {Skillstore},
  year = {2026},
  number = {10},
  url = {https://skillstore.io/skills/crearize-develop-backend/audits/10},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "develop-backend security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
  - name: "Crearize"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/crearize-develop-backend/audits/10"
identifiers:
  - type: other
    value: "skillstore:crearize-develop-backend:audit:10"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Add a new REST endpoint

Follow the project sequence for DTOs, controllers, services, mappers, tests, and OpenAPI updates.

Change a database model

Plan Flyway migrations, mapper changes, database documentation, and regression tests in one workflow.

Review implementation readiness

Check branch state, issue linkage, lint results, coverage, server startup, and final reporting before handoff.

Try These Prompts

Create a small endpoint

Use develop-backend to implement a read-only Spring Boot endpoint for [feature]. Include DTOs, service logic, mapper changes, tests, and OpenAPI updates.

Add schema-backed behavior

Use develop-backend for [feature] that needs a new table. Plan Flyway migration, entity, mapper XML, service rules, error codes, and tests.

Refactor backend logic

Use develop-backend to refactor [service area]. Preserve API behavior, reuse product.util helpers, remove duplicate logging, and verify lint, tests, and coverage.

Prepare release handoff

Use develop-backend to finish [issue number]. Validate server startup, endpoint behavior, migration application, documentation updates, and completion report contents.

Best Practices

Confirm branch and issue context before changing backend files.
Search for existing utilities and patterns before adding new classes.
Run lint, tests, coverage, and server startup checks before reporting completion.

Avoid

Do not duplicate request, response, SQL, or trace logging already handled by AOP.
Do not suppress warnings except for the documented Mockito generic exchange case.
Do not skip database, OpenAPI, or error-code documentation when behavior changes.

Frequently Asked Questions

What stack does this skill target?

It targets Spring Boot backends that use MyBatis, Flyway, Gradle, JUnit, Mockito, and project-specific documentation.

Does it write frontend code?

No. It focuses on backend API, service, database, mapper, validation, test, and documentation work.

How does it avoid duplicate code?

It tells the agent to inspect existing utilities, logging aspects, and exception handlers before adding new implementation.

What verification does it require?

It requires IDE warning review, Gradle checks, test success, coverage targets, and server startup verification.

Can it update database documentation?

Yes. It includes Flyway migration planning and database design document updates when schema changes are needed.

Should commands run automatically?

No. Git and Gradle commands should be reviewed, especially when the repository or dependencies are untrusted.

Developer Details

Author

Crearize

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/Crearize/ProjectTemplate/tree/main/.claude/skills/develop-backend

Ref

0519034dad657fb1f7706e0550e962beeda73fdf

Maintenance freshness

7/18/2026

Usage

10 downloads · 212 views

File structure

Build Better Go Tests

by 89jobrien

Go teams need consistent tests across units, integrations, mocks, benchmarks, and coverage. This skill provides practical Go testing patterns that Claude, Codex, and Claude Code can apply during development.

Coding & Development View

develop-backend

Install with my Agent

Agent-readable resources

Test it

Security Audit

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Add a new REST endpoint

Change a database model

Review implementation readiness

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details

More from Crearize

fix-bug

review-architecture

create-pr

generate-api-client

figma-to-tailwind

refactor-code

Related Skills

testing

alibaba-java-coding-guidelines-skill

senior-backend

testing-patterns

systematic-debugging

golang-testing