“Please take a look at the new article as it is in the wrong position.” “Please check to see if any old charges remain.”Even if the host just wants to know the cause or status, an AI that can manipulate files may proceed to fix it.
The first step to safely using Codex or Claude Code is not to memorize difficult commands.Separate requests to investigate and requests to change.
In this article, we will divide work on an inn site into four stages: “research,” “proposal,” “draft,” and “actual changes.” We will explain how much AI work should be done at each stage.
- Conclusion: You cannot proceed to the end with just one request.
- Just “investigating” the scope is ambiguous
- Stage 1: Investigate the current state
- Step 2: Compare fixes
- Stage 3: Create a draft outside of production
- 4th stage: Reflect only approved targets in production
- Differentiate between “may be fixed” and “may be published”
- How to say when you want to stop halfway
- Points to see in AI completion report
- Common mistakes
- What to write every time and what to leave in the operational rules
- Summary
- Reference materials
Conclusion: You cannot proceed to the end with just one request.
The basic flow is as follows.
1. Investigation: Check the current condition and cause
↓ Host reads the report
2. Suggestions: Compare fixes, impacts, and reversals
↓ The host chooses the method
3. Draft: Create local manuscripts and proposed changes
↓ Host confirms the contents
4. Production changes: Only reflect approved targets
↓ AI and host check the display
By dividing the stages, you can see where the AI made a mistake in recognition. You can also add conditions or go back to the previous step.
Just “investigating” the scope is ambiguous
When it comes to people, “Keep an eye on me” can be understood as just confirmation. However, for an AI that has access to work folders and the production environment, the boundaries of the next request are ambiguous.
Please take a look at the new articles on the top page.
It is not stated how far “viewing” includes investigation, file editing, setting changes, cache deletion, and actual production confirmation. In a safe request, add not only the purpose but also “how far this time.”,
Please investigate why the new articles on the top page are displayed differently than before.
This time it's just reading and reporting.
Do not make any changes to your files, WordPress, settings, cache, or production site.
Stop when you indicate possible causes, evidence you have seen, proposed fixes, and scope of impact.
Stage 1: Investigate the current state
What you can ask at this stage
- Read public pages and existing manuscripts
- Check related files and setting values
- Check posts, categories, links, and HTTP responses
- Find the difference before and after the change
- Organize possible causes and missing information
What not to do at this stage
- File editing
- Change WordPress posts and settings
- Plugins, themes, and PHP updates
- Delete cache and restart
- Send to external services
Copy-paste prompt
Please investigate [symptoms and things you want to check].
Target URL: [URL]
Date and time noticed: [Date and time/unknown]
Last change: [Change content/Unknown]
Please indicate the current condition, the difference from the expected condition, and possible causes, along with any evidence you have confirmed.
Separate speculation from confirmed facts.
Please only read and report this time and do not modify any files, WordPress, servers, or external services.
Please stop at the point where you suggest a correction.
Even if you write “read only”, it does not limit the permissions that the AI can use. Permissions and execution paths are arranged separately using Production server permission design and Restricted WP-CLI wrapper.
Step 2: Compare fixes
Even if you know the cause, there is no need to fix it right away. With WordPress, there are multiple ways to make changes, including the admin screen, child themes, custom CSS, and plugins. We will compare methods that are difficult to erase with updates and methods that are easy to restore.
Items to be shown to AI
| Item | Contents to confirm |
|---|---|
| What to change | Which posts, files, and settings to change |
| Not applicable | What should not be changed |
| Effects | What and how to fix it |
| Impact | Impact on other pages, reservations, and inquiries |
| Danger | What can happen if it fails |
| Backup | What to save |
| How to go back | Is it possible to go back when there is a problem |
| How to check | What to look for after changes |
Next request
We have confirmed the survey results. Don't change it yet and compare the fixes.
For each proposal, please indicate what is to be changed, what is not, effects, amount of work, risks, necessary backups, and how to restore.
Please also check the impact on reservations, inquiries, emails, and smartphone display.
Please suggest the safest option with a reason and do not implement it until I choose a method.
AI recommendations may not necessarily match the circumstances of the accommodation. The host adds on-site conditions such as “I don’t want to change the maintenance target of the production company” or “I won’t update this week because it’s full.”
Stage 3: Create a draft outside of production
Once you have chosen a method, create as many deliverables as possible before applying them to production.
- Local Markdown manuscript for articles
- If the guidance is changed, the text before and after the correction
- For design, change proposals and screen samples
- Work plan and confirmation table for settings
- For code, targeted differences and test results
Copy-paste prompt
Please make only a draft for confirmation using the [selected idea].
Locations that can be changed: [Local manuscript, specified file, etc.]
Places you should not change: Production WordPress, server settings, external services
Conditions to follow: [Existing design, reservation line, writing style, etc.]
If you want to overwrite an existing file, please indicate the target and difference first.
After creation, please report the changes, unconfirmed items, test results, and points to note when applying to production.
Please do not publish or send externally yet.
Beginners start with a practice folder or new draft file. The meaning of “local” and “open folder” is explained in Introduction to VS Code for the host.
4th stage: Reflect only approved targets in production
Before proceeding with production changes, the host will verify the following:
- Is the target to be repaired correct?
- Are the new texts and images correct?
- Is the number of changes as expected?
- Is there a way to properly back up and restore?
- Is now a good time to work?
- Will it affect reservations and inquiries?
Don’t just say “I have confirmed the contents”, write specifically what you have approved.
I only accept the following changes:
Target: [Post name, slug, file, etc.]
Approved content: [Manuscript, images, links, settings]
Number of items that can be changed: [1 item, etc.]
Not applicable: Other articles, themes, plugins, server settings, reservation/customer/payment data
Please take a backup and confirm successful completion and consistency before making any changes.
Please check the target, current value, and changed value again before executing.
If there is a difference in the number of items, backup failures, or unconfirmed items, please stop without executing.
After completion, please report what you changed and what you didn't change, HTTP response, PC/smartphone display, and how to change it back.
The specific flow of article publishing can be confirmed at From backup to article publication/display confirmation.
The items to check before approving publication are summarized in Checklist to check with AI before actual publication.
Differentiate between “may be fixed” and “may be published”
Modifying a file, registering it with WordPress, and making it publicly available are separate operations.
| Instructions | Permitted range |
|---|---|
| Create a manuscript draft | New text draft |
| Correct the local manuscript | Up to the specified manuscript in the work folder |
| Register drafts to WordPress | Create private drafts on the admin screen |
| Publish | Change to a state where general readers can see |
If you do not want to be allowed to publish an article just by asking them to create an article, please specify this in the operational rules. Conversely, even if you have permission to publish, deletions, refunds, reservation changes, etc. are subject to separate approvals.
How to say when you want to stop halfway
If the AI’s work is not what you intended, stop without waiting until the end of the explanation.
Please stop working.
Please do not make any further changes to your files, WordPress, servers, or external services.
Please report what you have confirmed so far, what you have changed, and what you have not completed.
Please do not perform the undo operation yet, but only indicate the necessary steps.
The reason why we do not restore it automatically is because there is a possibility that new reservations or inquiries have been received after the change. Restoration is also treated as a production change.
Points to see in AI completion report
You can’t judge how far you’ve come just by saying “Completed.”Let me report the following.
- The requested steps and the actual steps
- Target read
- Changed posts/files/settings
- Unchanged target
- Backup success/failure and consistency
- Tests performed and results
- Contents confirmed on PC/smartphone
- unconfirmed matters, failures, remaining work
Even if the command is successful, it does not necessarily mean that the public screen is correct.HTTP/SEO/Smartphone confirmation after publication will be performed as a series of tasks.
Common mistakes
Fix it “on the side” during the investigation
Even small typos or broken links will be reported as candidates during the investigation request. When unrelated changes are mixed together, it becomes difficult to isolate the cause when a problem occurs.
Assign multiple problems at once
We do not mix new layouts, login authentication, reservation system, and SEO into one request. Because the targets and risks are different, conversations and tasks are divided.
I consider the backup to be successful.
“The backup command was executed” and “normal restored data was created” are different. Check the success conditions you have decided on, such as completion status, checksum, and recorded content.
Restore immediately if a problem occurs
Restoration may result in the loss of reservations, inquiries, and orders placed after the change. Review the affected area and current data and approve the restoration.
What to write every time and what to leave in the operational rules
The target URL, article name, symptoms, and approval details for this time will be written in each request. The following principles to follow every time can be left in AGENTS.md or CLAUDE.md.
- Do not change in investigation request
- Check for successful backups before production changes
- Publication, deletion, restoration, and permission changes are approved by humans.
- Do not provide confidential information or customer information in answers
- After changing, check the public screen on PC and smartphone
How to install the file and free templates are provided in Safety Rules for AI Site Management.
Summary
When you let AI help you with your accommodation site, you need to differentiate between “investigate”, “choose how to fix it”, “create a draft outside of production”, and “reflect only what you approve”.At each stage, tell the AI what can and cannot be changed, and where the AI will stop.
If you still don’t know what to ask for, please see Introduction to Codex/Claude Code Consultation, 10 WordPress Operation Prompts for request texts by purpose, and Failures that have occurred in AI operation and tasks that should not be left to you for actual failures.
Reference materials
- OpenAI official: Agent approvals & security
- Anthropic official: Claude Code Security
- Anthropic Official: Claude Code Best Practices
Note: AI tool authority and approval screen may change. When using it, please check the official materials, the server you are contracted with, and the WordPress operating rules.
