App 自动化

Scan all of the `~/.codex/sessions` files from the past day and if there have been any issues using particular skills, update the skills to be more helpful. Personal skills only, no repo skills. If there’s anything we’ve been doing often and struggle with that we should save as a skill to speed up future work, let’s do it. Definitely don't feel like you need to update any- only if there's a good reason! Let me know if you make any.

Look at the latest remote origin/master or origin/main . Then produce an exec briefing for the last 24 hours of commits that touch <DIRECTORY> Formatting + structure: - Use rich Markdown (H1 workstream sections, italics for the subtitle, horizontal rules as needed). - Preamble can read something like “Here’s the last 24h brief for <directory>:” - Subtitle should read: “Narrative walkthrough with owners; grouped by workstream.” - Group by workstream rather than listing each commit. Workstream titles should be H1. - Write a short narrative per workstream that explains the changes in plain language. - Use bullet points and bolding when it makes things more readable - Feel free to make bullets per person, but bold their name Content requirements: - Include PR links inline (e.g., [#123](...)) without a “PRs:” label. - Do NOT include commit hashes or a “Key commits” section. - It’s fine if multiple PRs appear under one workstream, but avoid per‑commit bullet lists. Scope rules: - Only include changes within the current cwd (or main checkout equivalent) - Only include the last 24h of commits. - Use `gh` to fetch PR titles and descriptions if it helps. Also feel free to pull PR reviews and comments

--- name: recent-code-bugfix description: Find and fix a bug introduced by the current author within the last week in the current working directory. Use when a user wants a proactive bugfix from their recent changes, when the prompt is empty, or when asked to triage/fix issues caused by their recent commits. Root cause must map directly to the author’s own changes. --- # Recent Code Bugfix ## Overview Find a bug introduced by the current author in the last week, implement a fix, and verify it when possible. Operate in the current working directory, assume the code is local, and ensure the root cause is tied directly to the author’s own edits. ## Workflow ### 1) Establish the recent-change scope Use Git to identify the author and changed files from the last week. - Determine the author from `git config user.name`/`user.email`. If unavailable, use the current user’s name from the environment or ask once. - Use `git log --since=1.week --author=<author>` to list recent commits and files. Focus on files touched by those commits. - If the user’s prompt is empty, proceed directly with this default scope. ### 2) Find a concrete failure tied to recent changes Prioritize defects that are directly attributable to the author’s edits. - Look for recent failures (tests, lint, runtime errors) if logs or CI outputs are available locally. - If no failures are provided, run the smallest relevant verification (single test, file-level lint, or targeted repro) that touches the edited files. - Confirm the root cause is directly connected to the author’s changes, not unrelated legacy issues. If only unrelated failures are found, stop and report that no qualifying bug was detected. ### 3) Implement the fix Make a minimal fix that aligns with project conventions. - Update only the files needed to resolve the issue. - Avoid adding extra defensive checks or unrelated refactors. - Keep changes consistent with local style and tests. ### 4) Verify Attempt verification when possible. - Prefer the smallest validation step (targeted test, focused lint, or direct repro command). - If verification cannot be run, state what would be run and why it wasn’t executed. ### 5) Report Summarize the root cause, the fix, and the verification performed. Make it explicit how the root cause ties to the author’s recent changes.

Check my commits from the last 24h and submit a $recent-code-bugfix.