- Home
- Skills
- Agents & Orchestration
- Approval Gated Integration
More screenshots
Works with the AI Agents you already use
Approval Gated Integration
Move complex code changes forward with clear checkpoints and human approval.
$5
Approval Gated Integration
Example session with this skill installed
Use $approval-gated-integration to refactor email delivery behind an interface. Inspect the existing code, propose small steps, and wait for my approval before applying each step. Preserve current behavior and run focused checks after every approved change.
- Read your context and instructions
- Compiled the approval gated integration
I have inspected the current email-delivery code, SMTP integration, and existing tests. I have initialized a progress ledger in this conversation to track the refactor. No implementation changes have been applied.
Implementation Plan: Email Delivery Refactor
| ID | Step | Scope | Status |
|---|---|---|---|
| 1 | Add Delivery Interface | Define the delivery contract, wrap the existing SMTP implementation, and add focused adapter tests | proposed |
| 2 | Migrate Password-Reset Emails | Update password-reset callers to use the delivery interface and verify existing behavior | proposed |
| 3 | Migrate Billing Emails and Clean Up | Update billing callers, verify their behavior, and remove obsolete direct SMTP references from migrated callers | proposed |
Step 1 is the next approval decision. Steps 2 and 3 are proposed follow-up work and remain unapproved.
Step 1: Add Delivery Interface
- Objective: Establish a delivery contract backed by the existing SMTP implementation.
Behavioral changes: No observable change to email delivery. Existing callers keep their current delivery path until their migration is approved.
- Affected files:
sender.ts,smtp-adapter.ts,sender.test.ts. - Schema or migration implications: None; no database changes.
Validation: Run the project's type check and focused sender/adapter tests to verify that the adapter preserves existing SMTP behavior and error handling.
Risks: Low. The interface and adapter do not replace existing callers in this step. Tests must confirm that SMTP errors still reach the caller.
Tradeoff: The existing delivery path and new adapter coexist until the caller migrations are approved and completed.
Next steps
- Say "Approve step 1" to begin adding the interface, adapter, and focused tests.
- Provide feedback if you want to change the scope or include additional delivery methods in the contract.
- Ask to see the proposed interface definition before I write the files.
Connects securely to your tools. The creator never sees your data.
About this skill
Move complex code changes forward with clear checkpoints and human approval.
Approval-Gated Integration guides your coding agent through small, reviewable steps. It inspects the existing repository before proposing a change, follows the project's conventions, and explains what each step will do, which areas it affects, how it will be checked, and what tradeoffs matter.
You approve the scope before implementation. The agent applies only the approved step or explicitly approved group of steps, preserves unrelated work, and keeps optional improvements separate. If a newly discovered dependency materially changes the scope or risk, it stops and brings that decision back to you.
After each implemented step, the agent runs focused checks and updates a progress ledger with the status, validation, and result. You can see what is finished, what is blocked, and what still needs approval. Approved groups of steps are implemented and checked sequentially.
Use it to add a feature incrementally, refactor a module, migrate persistence, or introduce an architectural change while retaining oversight. Full integration checks, production builds, and full test suites run after the final implementation step only when you explicitly request them. Documentation is created only when requested.
The outcome is an implementation you have reviewed as it develops, with validation evidence at each step and a concise final handoff.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Requires a local environment capable of running tests/linters. Does not automatically generate documentation or PRs without explicit user instructions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago
Permissions
File Scopes
Works across the codebase. Only files within each approved step’s scope are modified.