skills.rest
lemonhall
lemonhallCOMMUNITY
Explore all skills by this author →
GitHub

watchdog-approvals

Persist user-approved safe actions into Codex approvals across sessions.

5|1|Updated Jan 28, 2026
Search Tags:#automation#codex#trust#approvals#allowlist#watchdog
One-click install
npx skills add https://github.com/lemonhall/tashan-development-loop --skill watchdog-approvals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: watchdog-approvals
Source: https://github.com/lemonhall/tashan-development-loop/tree/main/watchdog-approvals
Command: npx skills add https://github.com/lemonhall/tashan-development-loop --skill watchdog-approvals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps persistently approve safe automation actions within Codex so future sessions don't re-ask for the same low-risk tasks.

Core Features & Use Cases

  • Persist approved actions to bypass repeated prompts.
  • Define and manage a minimal allowlist of safe commands with rollback.
  • Provides auditability and reversible changes across projects.

Quick Start

Enable approval persistence by confirming a safe action now, then test a repeating task to confirm future prompts are silenced.

Frequently Asked Questions about watchdog-approvals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop Codex from repeatedly asking for approvals on safe commands?▼

You can stop repeated Codex approvals by persisting user-approved safe actions into an allowlist, which automatically bypasses confirmation prompts for repetitive tasks like running tests, reading logs, and git operations across future sessions.

Can I roll back an action I approve in the Codex automation allowlist?▼

Yes, the Codex automation allowlist supports rollback and auditability, ensuring that any persistent approval changes you make for safe actions are fully explainable and reversible across your projects.

What is the best way to persist safe git operations across multiple Codex sessions?▼

The best way to persist safe git operations is to define a minimal allowlist within Codex approvals, confirming a safe action once so that future sessions automatically bypass repeated confirmation prompts for those same low-risk tasks.

Does Codex approval persistence work for repetitive tasks like reading logs and running tests?▼

Yes, Codex approval persistence works specifically for repetitive, low-risk tasks like running tests, reading logs, and performing git operations within a project, silencing future prompts by storing approved actions in a minimal allowlist.

When should I not use persistent approvals for Codex automation?▼

You should not use persistent approvals for high-risk or non-repetitive Codex automation tasks, as this skill specifically targets repetitive, low-risk actions and stores them in a minimal allowlist to prevent repeated confirmation prompts safely.

Related Skills

Explore More Software Engineering Skills→
jay6697117jay6697117

agency-automation-governance-architect

Evaluate n8n automation requests against value, risk, and compliance criteria.

Community
Advanced
open-gitagentopen-gitagent
2.9k

packet-factory

Create, review, and dispatch atomic work packets with approval and scope locking.

Official
Intermediate
billydeeii136billydeeii136

ship

Automates CI/CD including testing, code review, version management, PR creation, and deployment for Git/GitHub/GitLab workflows.

Community
Advanced
settlemintsettlemint
5

todo-tracking

Create and manage persistent file-based todo items in .claude/todos.

Official
Intermediate