Codex App Pack

Open this repo and orient yourself before changing anything.

Repo path:
[PASTE PATH]

Do:
1. Confirm the working directory
2. Read README, AGENTS.md, package files, and obvious docs
3. Check git status
4. Summarize the app, build commands, and likely risk areas
5. Ask before editing if the target is still ambiguous

Inspect the code for this request before implementing:
[DESCRIBE REQUEST]

First report:
1. Files that look relevant
2. Existing patterns to follow
3. Commands needed to verify the work
4. Any unrelated dirty git changes you notice

Then make the smallest safe implementation plan.

Review this repo and create or update AGENTS.md for future Codex sessions.

Include:
1. Project purpose
2. Build, test, lint, and run commands
3. Important directories
4. Editing conventions
5. Verification expectations
6. Things Codex must not do without asking

Keep it specific to this repo, not generic.

Make a plan for this work:
[DESCRIBE GOAL]

The plan should include:
1. What you will inspect
2. What files you expect to edit
3. Risks and unknowns
4. Verification commands
5. A stopping point where I should review

After the plan, wait only if a decision is genuinely needed. Otherwise implement it.

Implement this feature:
[DESCRIBE FEATURE]

Constraints:
1. Follow existing patterns
2. Keep the change scoped
3. Do not refactor unrelated code
4. Update docs only if needed
5. Run the most relevant verification command

At the end, summarize changed files and proof.

Fix this bug:
[DESCRIBE BUG AND STEPS TO REPRODUCE]

Please:
1. Reproduce or inspect the likely failure path
2. Identify the root cause
3. Patch the smallest responsible code
4. Add or update a test if practical
5. Run verification and show the important result
6. Mention any remaining risk

Add or update tests for:
[DESCRIBE BEHAVIOR]

Before editing, find the repo's current test style.

Then:
1. Add focused coverage
2. Avoid broad rewrites
3. Run the relevant tests
4. If no test framework exists, explain the lightest practical verification instead

Review my current diff like a senior engineer.

Focus on:
1. Bugs or regressions
2. Missing tests
3. Security or data risks
4. Accessibility or UX issues, if relevant
5. Build or deployment problems

Lead with findings by severity and include file/line references where possible.

For this task, check whether a Codex skill or plugin is available and useful:
[DESCRIBE TASK]

If one fits:
1. Name it
2. Explain why it applies
3. Use it according to its instructions
4. Keep the implementation aligned with this repo

If none fits, continue with the normal repo workflow and say so briefly.

Help me set up a Codex automation, if automations are enabled in this app.

Recurring task:
[DESCRIBE TASK]

Please define:
1. The exact prompt
2. The schedule
3. The workspace or repo it should run in
4. What result I should review
5. What it must not change without approval

Verify this local web page after implementing the change:
[URL OR ROUTE]

Check:
1. Desktop rendering
2. Mobile rendering
3. Dark mode, if the site supports it
4. Console errors
5. The exact user interaction affected by the change
6. Screenshots or a clear visual summary

Use a branch or worktree workflow if supported and appropriate for this task:
[DESCRIBE TASK]

Before starting:
1. Check current git status
2. Avoid overwriting unrelated changes
3. Explain where the work will happen
4. Keep changes scoped to the task
5. Summarize how to review or merge the result

Prepare this as a Codex cloud task, if Codex cloud is enabled for my workspace:
[DESCRIBE TASK]

Include:
1. Repository and branch
2. Setup or test commands
3. Files or areas to inspect
4. Definition of done
5. Internet access needs, if any
6. What should come back for review

Prepare this work for a pull request.

Do:
1. Review git diff
2. Run the relevant checks
3. Write a concise PR summary
4. List tests or verification performed
5. Note risks or follow-up work
6. Do not push or create the PR unless I ask

Investigate this PR or CI failure:
[LINK OR DETAILS]

If GitHub access is enabled, inspect the relevant checks and files.

Return:
1. Most likely cause
2. Exact failing command or check
3. Files involved
4. Proposed fix
5. Whether the fix should be local, cloud, or GitHub follow-up work

Review whether this Codex task needs internet access:
[DESCRIBE TASK]

Tell me:
1. Whether internet access is actually needed
2. Which domains or package registries are required
3. What could be done offline
4. Security or supply-chain risks
5. The narrowest safe access policy, if access is enabled

Create a handoff note for this work.

Save it as a repo file only if that makes sense for the project; otherwise summarize it in chat.

Include:
1. Goal
2. Current status
3. Files changed
4. Commands run
5. Errors or blockers
6. Next recommended steps
7. Anything another agent must avoid touching

Help me recover from this failed run:
[PASTE ERROR OR DESCRIBE FAILURE]

Please:
1. Identify the likely failure category
2. Check whether any files were partially changed
3. Preserve useful logs or context
4. Propose the smallest next command
5. Avoid destructive cleanup unless I explicitly approve it

Summarize the work from this Codex session.

Include:
1. What changed
2. Files edited
3. Commands run and results
4. What was not completed
5. Known risks
6. Suggested next commit message
7. Suggested next task

Make a safe revert plan for this repo.

I want to undo:
[DESCRIBE WHAT TO UNDO]

Before changing anything:
1. Inspect git status and diff
2. Separate your changes from unrelated user changes
3. Identify the exact files and hunks to revert
4. Propose a non-destructive approach
5. Ask before running any destructive git command