production-safe-loops
Skill from simbaTmotsi/simba-skills
Install
npx skills add simbaTmotsi/simba-skills --skill production-safe-loops
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add simbaTmotsi/simba-skills
/plugin install simba-skills@simba-skills
This skill is part of the plugin “simba-skills”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the production-safe-loops skill do?
Description from the SKILL.md in the source repository.
Questions about production-safe-loops
What does the production-safe-loops skill do?
Check what a feedback loop will actually write to before running it, and refuse to run it against production. Use before running a test suite with database fixtures, a repro or curl loop, a replay script, a stress loop ("loop the trigger 100x, parallelise"), a migration, an import, or a seed script. Use whenever you are about to run tests, build a repro loop, or debug against a running system, and especially when following TDD or bug-diagnosis skills (such as `tdd` or `diagnosing-bugs`) in a repo whose live deployment runs on the same host, shares its `.env`, or is reachable from the shell.
How do I install production-safe-loops?
In a terminal: npx skills add simbaTmotsi/simba-skills --skill production-safe-loops. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use production-safe-loops?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is production-safe-loops safe to use?
Our automatic check found patterns worth a look (see “Check”). That is not proof of anything bad – read the SKILL.md and scripts before installing.
More skills from simbaTmotsi/simba-skills
Audit Claude Code permission settings for leaked credentials, stale temp-path rules, risky allow rules and rule pile-up, then clean up what you approve.
Lint Claude Code skills and subagents for files that never load, risky skills missing a manual-only guard, drifted copies of upstream skills, and name collisions.
Draft a compliant upstream bug report when a skill from Matt Pocock's skills repo (mattpocock/skills: tdd, diagnosing-bugs, grill-with-docs, to-spec, to-tickets, implement, code-review, and the rest) does the wrong thing in a real …
Deploy a project to production with pre-flight checks, a database backup, verification, and a written rollback note.
Set up or review routine maintenance on a self-hosted Docker box (Postgres backups, disk alerts, Docker cleanup, hardening).
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.