fix(claude/commands): improve line wrapping for 80-char line length

Reflow long lines in command files to stay within 80 characters,
matching the project's line length convention. Also fix lowercase
"markdown" to "Markdown" in refactor-agents.md.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-08 17:22:22 +00:00
parent d84f91ba3a
commit 623e3896e6
5 changed files with 24 additions and 18 deletions

View File

@@ -55,8 +55,8 @@ Convert this project's `CLAUDE.md` into an `AGENTS.md` file, and replace
6. **Summary**: Report what was done, including any references that were updated
in step 3. Stop here.
7. **Create `CLAUDE.md` reference** (only reached when `CLAUDE.md` doesn't
exist but `AGENTS.md` does):
7. **Create `CLAUDE.md` reference** (only reached when `CLAUDE.md` doesn't exist
but `AGENTS.md` does):
- Write a new `CLAUDE.md` in the project root containing just:
```
@AGENTS.md

View File

@@ -5,17 +5,19 @@ source: https://github.com/anthropics/claude-plugins-official/blob/main/plugins/
## Your Task
You need to execute the following bash commands to clean up stale local branches that have been deleted from the remote repository.
You need to execute the following bash commands to clean up stale local branches
that have been deleted from the remote repository.
## Commands to Execute
1. **First, list branches to identify any with [gone] status**
Execute this command:
1. **First, list branches to identify any with [gone] status** Execute this
command:
```bash
git branch -v
```
Note: Branches with a '+' prefix have associated worktrees and must have their worktrees removed before deletion.
Note: Branches with a '+' prefix have associated worktrees and must have
their worktrees removed before deletion.
2. **Next, identify worktrees that need to be removed for [gone] branches**
Execute this command:
@@ -23,8 +25,8 @@ You need to execute the following bash commands to clean up stale local branches
git worktree list
```
3. **Finally, remove worktrees and delete [gone] branches (handles both regular and worktree branches)**
Execute this command:
3. **Finally, remove worktrees and delete [gone] branches (handles both regular
and worktree branches)** Execute this command:
```bash
# Process all [gone] branches, removing '+' prefix if present
git branch -v | grep '\[gone\]' | sed 's/^[+* ]//' | awk '{print $1}' | while read branch; do

View File

@@ -14,13 +14,15 @@ source: https://github.com/anthropics/claude-plugins-official/blob/main/plugins/
Based on the above changes:
1. Create a new branch if on main. If already on a non-main branch,
check if the branch name looks randomly generated (e.g. UUIDs,
hex strings, meaningless character sequences, or 1-3 random
unrelated words like "brave-fox" or "purple-mountain") rather than
descriptive of the changes. If so, rename it to something that
aligns with the changes using `git branch -m <new-name>`.
1. Create a new branch if on main. If already on a non-main branch, check if the
branch name looks randomly generated (e.g. UUIDs, hex strings, meaningless
character sequences, or 1-3 random unrelated words like "brave-fox" or
"purple-mountain") rather than descriptive of the changes. If so, rename it
to something that aligns with the changes using `git branch -m <new-name>`.
2. Create a single commit with an appropriate message
3. Push the branch to origin
4. Create a pull request using `gh pr create`
5. You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
5. You have the capability to call multiple tools in a single response. You MUST
do all of the above in a single message. Do not use any other tools or do
anything else. Do not send any other text or messages besides these tool
calls.

View File

@@ -15,4 +15,6 @@ source: https://github.com/anthropics/claude-plugins-official/blob/main/plugins/
Based on the above changes, create a single git commit.
You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
You have the capability to call multiple tools in a single response. Stage and
create the commit using a single message. Do not use any other tools or do
anything else. Do not send any other text or messages besides these tool calls.

View File

@@ -20,10 +20,10 @@ Follow these steps:
3. **Group the rest**: Organize remaining instructions into logical categories
(e.g., TypeScript conventions, testing patterns, API design, Git workflow).
For each group, create a separate markdown file.
For each group, create a separate Markdown file.
4. **Create the file structure**: Output:
- A minimal root AGENTS.md with markdown links to the separate files
- A minimal root AGENTS.md with Markdown links to the separate files
- Each separate file with its relevant instructions
- A suggested .agents/docs/ or docs/ folder structure