chore(deps): update agent skills#68
Conversation
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dc6f3e29f1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| You must have a branch from the stack checked out locally. The command targets the active stack — the one that contains the currently checked out branch. | ||
| With no argument, the command targets the active stack — the one containing the currently checked out branch — unstacking it on GitHub and removing local tracking. | ||
|
|
||
| Provide a stack number to unstack a specific stack on GitHub. This works from anywhere in the repository, whether or not the stack is checked out locally — the number is unstacked directly through the GitHub API (like `gh stack link`, no local tracking required). If the stack is also tracked locally, its local tracking is removed as well. |
There was a problem hiding this comment.
For stacks that contain queued or auto-merge-enabled PRs, this overstates what unstack <number> does: the v0.0.8 README says those PRs stay stacked and, when any PRs remain, local tracking is unchanged (reference). An agent following this skill would immediately run gh stack init assuming both GitHub and local stack state are gone, which can leave stale stack state in place and derail a restructure; please include the partial-unstack caveat here.
Useful? React with 👍 / 👎.
| | View stack details (JSON) | `gh stack view --json` | | ||
| | Switch branches up/down in stack | `gh stack up [n]` / `gh stack down [n]` | | ||
| | Switch to top/bottom branch | `gh stack top` / `gh stack bottom` | | ||
| | Check out by stack number | `gh stack checkout 7` | |
There was a problem hiding this comment.
This new quick-reference row adds stack-number checkout, but the detailed checkout guidance below still says the command accepts only a PR number or branch and the limitations section still says remote checkout requires a PR number. The official v0.0.8 docs list gh stack checkout [<stack-number> | <pr-number> | <pr-url> | <branch>] (reference), so agents that rely on the detailed section can reject the new stack-number path or incorrectly fall back to PR lookup.
Useful? React with 👍 / 👎.
dc6f3e2 to
efc93fe
Compare
1 participant
Automated update of agent skills to their latest versions.
Updated files under
plugins: