Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

guardrails

Sterne2

Forks1

Aktualisiert7. Februar 2026 um 17:45

Use for change discipline, validation expectations, and safety checks when making repo changes.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

lmiguelvargasf

lmiguelvargasf/kerly

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	guardrails
description	Use for change discipline, validation expectations, and safety checks when making repo changes.

Guardrails

When to use

You are planning changes that might touch multiple areas or risk unintended churn.
You are preparing to declare work complete and need validation guidance.

Steps

Keep changes small and incremental; avoid drive-by refactors.
Touch the fewest files necessary; avoid cross-module churn.
Follow existing patterns and conventions; do not invent new architecture.
If behavior changes, add/update tests to cover it.
Use Taskfile targets for validation:
- Backend: task backend:format, task backend:lint, task backend:typecheck, task backend:test.
If a check can’t run, state what ran and what was blocked.

Constraints and guardrails

Never commit secrets or real credentials (use .env.example).
Ask/confirm before changes to:
- API, auth/session/security logic, or data model/migrations
- Dependencies or lockfile changes not required by the task

References

.env.example
Taskfile.yml
backend/Taskfile.yml

Mehr aus diesem Repository

gleiches Repository

workflow-taskfile

lmiguelvargasf/kerly

Use when running installs, dev servers, tests, lint/format, codegen, or Docker lifecycle tasks; Taskfile is the source of truth.

2026-02-072

sqlalchemy-code-review

lmiguelvargasf/kerly

Reviews SQLAlchemy code for session management, relationships, N+1 queries, and migration patterns. Use when reviewing SQLAlchemy 2.0 code, checking session lifecycle, relationship() usage, or Alembic migrations.

2026-01-222

backend-async-tasks

lmiguelvargasf/kerly

Use when creating or updating Celery tasks, async job logic, or Beat schedules in the backend.

2026-01-172

web-design-guidelines

lmiguelvargasf/kerly

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

2026-01-172

name	guardrails
description	Use for change discipline, validation expectations, and safety checks when making repo changes.

Guardrails

When to use

You are planning changes that might touch multiple areas or risk unintended churn.
You are preparing to declare work complete and need validation guidance.

Steps

Keep changes small and incremental; avoid drive-by refactors.
Touch the fewest files necessary; avoid cross-module churn.
Follow existing patterns and conventions; do not invent new architecture.
If behavior changes, add/update tests to cover it.
Use Taskfile targets for validation:
- Backend: task backend:format, task backend:lint, task backend:typecheck, task backend:test.
If a check can’t run, state what ran and what was blocked.

Constraints and guardrails

Never commit secrets or real credentials (use .env.example).
Ask/confirm before changes to:
- API, auth/session/security logic, or data model/migrations
- Dependencies or lockfile changes not required by the task

References

.env.example
Taskfile.yml
backend/Taskfile.yml