mode-readonly

Enforce read-only constraints during code review and debugging investigations.

5|1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/faroukBakari/trader-pro --skill mode-readonly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mode-readonly
Source: https://github.com/faroukBakari/trader-pro/tree/main/.github/skills/mode-readonly
Command: npx skills add https://github.com/faroukBakari/trader-pro --skill mode-readonly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only investigation mode prevents accidental modifications by enforcing a comprehensive set of non-destructive constraints during analysis.

Core Features & Use Cases

  • Enforces non-destructive constraints: DO NOT create, edit, delete, move, or rename files.
  • Allows read-only operations: read_file, grep_search, file_search, and non-destructive git inspections like status, log, diff, branch -l, show, blame.
  • Guidance and guardrails: pre-command checks before terminal actions; efficiency guidelines; investigation aids for safer code review and RCA.

Quick Start

Operate in read-only mode by verifying that no file or git state changes will be performed and proceed with read-only commands only.

Frequently Asked Questions about mode-readonly

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

FAQPage Schema
How do I perform a non-destructive git investigation during code review?

A non-destructive git investigation enforces read-only constraints to prevent accidental file or repository state changes. It allows safe operations like status, log, diff, and blame while blocking any file creation, editing, deletion, or movement.

What is read-only mode for debugging and root cause analysis?

Read-only mode for debugging applies pre-command checks to terminal actions, ensuring only safe inspections are executed. It guards against state changes by requiring explicit user verification before proceeding with any shell commands during RCA.

Can I use grep_search and file_search while enforcing read-only constraints?

Yes, you can use grep_search and file_search alongside read_file and non-destructive git inspections. These read-only operations are explicitly allowed, while creating, editing, deleting, moving, or renaming files is strictly prohibited.

What's the best way to ensure safe shell commands during repository analysis?

The best way to ensure safe shell commands is to apply pre-command checks before terminal actions and verify that no git state changes will occur. This enforces a strict read-only mode that guards against accidental modifications during analysis.

When should I use read-only constraints for code review?

You should use read-only constraints for code review, root cause analysis, debugging, and learning tasks when repository modifications are not allowed. This prevents destructive changes by enforcing non-destructive operations and explicit user verification.