Tabbit
活动资源博客模型
Tabbit LogoTabbit

Tabbit — 为你工作的 AI 浏览器

主题资源

  • AI Browser Resources
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Comparisons
  • AI Browser Alternatives
  • Browser Productivity Resources

热门指南

  • AI Browser
  • Agentic Browser Download
  • Best AI Browser 2026: Top 9 Tested & Ranked
  • AI Browser Download
  • Free AI Browser
  • Best AI Browser 2026
  • AI Browser Comparison 2026
  • AI Browser for Windows
  • AI Browser for Mac
  • Chrome Alternative 2026

活动

  • 别装了,你在《牛来》里早有原型
  • Tabbit 妙招大赛
  • KPOP SBTI 饭圈人格测试
  • Tabbit 校园共创者计划
  • fifi 的论文文献妙招精选
  • 用户问卷

关于

  • Tabbit 博客
  • 媒体报道
提示词
社区GPT-6 Astra

GPT-6 Astra:Codex 仓库指令审计完整提示词

原始来源

Reddit(r/codex)

作者IcyPiece6643

原文日期2026-09-05

Tabbit 整理2026-09-08

查看原文

一句话结论

这份完整提示词让 Codex 依据官方 Astra 指南审计并精简仓库指令,同时把修改范围严格限制在指令文件内。

适用场景

  • 适合的任务:升级仓库的 AGENTS.md、核对真实开发命令、减少不必要审批停顿、明确实现和修复任务的完成条件。

  • 不适合的任务:模型 API 迁移、修改应用内提示词、变更模型 ID、优化应用运行性能或自动修改全局配置。

  • 适用的模型版本:GPT-6 Astra;提示词要求结合当前官方 Codex 文档和 Astra prompting guidance。

  • 适用的客户端、Agent 或 API:安装 OpenAI Docs Skill 的 Codex CLI;其他客户端需要把 $openai-docs 调用替换成等价的官方文档访问方式。

  • 推荐的推理档位和参数:原帖未公开 effort、模型快照或 API 参数。

可直接使用的内容

$openai-docs

Improve the instructions that govern how Codex CLI works in this repository, using current official Codex documentation and GPT-6 Astra prompting guidance.

The goal is better implementation quality, reliable follow-through, fewer unnecessary approval pauses, and efficient use of context and verification.

This is a Codex workflow improvement task. Do not migrate this application's API integrations, change its model IDs, modify application prompts, or optimize its runtime performance.

1. Inspect the existing setup.

Read the applicable AGENTS.md and AGENTS.override.md files, repository-local Codex configuration, and relevant installed skill instructions. Inspect the README, package manifests, workspace structure, and CI configuration to establish the actual development and verification commands.

Identify conflicting instructions, redundant guidance, outdated commands, unnecessary stopping points, and missing repository knowledge. Distinguish verified problems from preferences.

2. Apply focused improvements.

Update the effective repository-level AGENTS.md, creating it if needed. Update nested instruction files only where their scope requires it. Preserve valid project constraints and existing uncommitted work.

Keep the instructions concise and specific to this repository. Include:

• A compact map of the important code locations and architectural boundaries.

• The actual package manager and supported development commands.

• Relevant test, typecheck, lint, build, and runtime verification commands, including prerequisites.

• Expectations for following existing patterns and avoiding unrelated changes.

• Clear completion criteria for implementation and bug-fix tasks.

Incorporate the applicable official prompting guidance:

• Carry authorized implementation through the relevant verification.

• Resolve routine, reversible choices without repeatedly seeking confirmation.

• Ask focused questions when an unresolved decision materially affects correctness, scope, or authorization.

• Respect higher-priority instructions and permission boundaries; explain the exact source of a blocking instruction.

• Match verification to the change and required project gates; repeat checks when new evidence warrants it.

• Report the result, verification evidence, and concrete remaining limitations concisely.

Avoid copying entire prompting guides, adding motivational boilerplate, or duplicating instructions already supplied by the harness.

3. Keep changes within scope.

Only edit repository instruction files for this task. Inspect global instructions and installed skills as needed, but report conflicts there without modifying them. Recommend any Codex configuration changes separately, with their documented benefits and tradeoffs.

4. Verify and finish.

Review the resulting instruction hierarchy for contradictions and confirm documented commands against repository scripts and CI. Clearly distinguish commands you actually ran from commands you only inspected.

Apply the authorized instruction edits now. Finish with a concise explanation of what changed, why it should help, the official sources used, and any unresolved conflicts. Do not claim measured performance improvements without a comparison.

使用方法与边界

  1. 先安装或启用能读取 OpenAI 官方文档的 Skill,再在目标仓库根目录运行。

  2. 提交前检查 diff,确认只修改了仓库指令文件,没有触碰应用提示词、模型配置或业务代码。

  3. 运行提示词中识别出的最小必要验证,并区分“实际执行”和“只从脚本中确认存在”的命令。

  4. 原帖公开了完整输入,但没有公开 Astra 的最终输出、修改 diff、测试结果或前后对照指标,因此属于可复制 prompt,不构成效果基准。

Tabbit 小编提醒

提示词内容来自公开资料与 Tabbit 编辑整理。引用前请查看原文授权与适用范围。

GPT-6 Astra

在 Tabbit 中使用

GPT-6 Astra

相关提示词

官方OpenAI Developers

OpenAI GPT-6 Astra 提示词与配置指南

官方OpenAI Developers

OpenAI GPT-6 Astra API 模型配置与成本边界

社区X2026-09-05

GPT-6 Astra:Skills 与 AGENTS.md 指令清理指南

GPT-6 Astra

相关测评

官方OpenAI 官方发布页

GPT-6 Astra:OpenAI 官方发布页的五项基准与 GPT-5.6 Sol 对照

官方Reddit(r/codex)与 OpenAI Codex GitHub issue 评论2026-09-08

GPT-6 Astra:子代理 30 秒轮询造成额度消耗的可复现遥测

媒体CodeRabbit Blog2026-09-04

GPT-6 Astra:CodeRabbit 代码审查中的跨文件缺陷与成本评测

社区Reddit(r/codex)2026-09-08

GPT-6 Astra:100K+ LOC 长任务、推理档位与 Fast 模式现场报告