/retro will now aggressively look for opportunities to turn fuzzy rules into deterministic checks
It'll propose custom lint rules, pre-commit hooks, or CI workflows.
Found an error? Do a /retro, and make it impossible next time
https://t.co/7PJwGitH3G
At Anthropic, Claude now writes 80% of our code. Engineers ship 8x more code per quarter.
Side effect: Tests grew 10x. CI jobs up 25x in 6 months. Here's what helped us scale:
https://t.co/WOL2r60vAE
Coming soon to mattpocock/skills
/retro
Gives you opportunities to improve your codebase, skills, and steering over time based on actual session data
Talking about this (among other things) at 8:30AM PT TODAY on this live stream:
https://t.co/uODv6tPv5a
I just published a manifesto for all the developers out there who use an AI coding tool, but feel like they're not shipping much faster
I wrote 10 principles for changing how you build software with AI, based on what I've seen work for teams across Amazon
https://t.co/smq7Rt5QkZ
群里看到的 Codex Tip,给对话批量改名。
---
Rename the conversations in the current Codex project. Only change conversation titles. Never touch the project name.
Rules:
- Date comes from the conversation's `createdAt`, converted to Asia/Shanghai. Do not use `updatedAt`.
- Format: `MMDD|TYPE|Topic`
- TYPE must be one of these. Use the English code by default. Use the Chinese label only if I ask for Chinese.
FEA / 功能 = feature
DES / 设计 = design
FIX / 修复 = bug fix
OPT / 优化 = optimization
REL / 发布 = release
EXP / 探索 = exploration
DOC / 文档 = docs
RES / 研究 = research
- Use one language for TYPE across all titles in a run. Never mix.
- Topic summarizes what the conversation is actually about. Do not repeat the project name.
- Keep titles short and specific. They show in the sidebar.
- If you cannot tell the topic, keep the original title. Do not guess.
- Change nothing else: not the project name, conversation content, project assignment, order, pin state, or archive state.
Examples (English, the default):
Before: Improve batch text display
After: 0903|OPT|Batch text display
Before: New feature discussion
After: 0901|DES|UI alignment check
Examples (Chinese, on request):
Before: 优化批次文字显示
After: 0903|优化|批次文字显示
Before: 提交代码到 GitHub
After: 0813|发布|提交代码到GitHub
Before making any change, output only a two-column table with this exact header:
| Before | After |
Wait for my confirmation. After renaming, report only the results.