文件操作 - SKILL.md

文件: /storage/v12552/stanleysteamer/public_html/wp-content/plugins/imagify/.claude/skills/groom/SKILL.md

编辑文件内容

---
name: groom
description: Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.
argument-hint: <issue-number>
---

# Groom

Standalone grooming for a single issue. Runs the full grooming analysis and writes the spec
to disk. Posting to GitHub is your choice — you are prompted at the end.

## Step 1 — Load config

Read project config from the orchestrator's `## Project Config` block:

```bash
ORCHESTRATOR=".claude/skills/orchestrator/SKILL.md"
REPO=$(grep '^REPO=' "$ORCHESTRATOR" | cut -d= -f2)
TEMP_ROOT=$(grep '^TEMP_ROOT=' "$ORCHESTRATOR" | cut -d= -f2)
```

## Step 2 — Sync the issue

Ensure the issue file exists at `{TEMP_ROOT}/issues/<N>/issue.md`. Run:

```bash
bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>
```

If the file already exists and is recent (less than 5 minutes old), skip the sync.

## Step 3 — Invoke the grooming agent

Invoke the `grooming-agent` sub-agent with the following invocation context:

> Issue number: `<N>`
> Runtime values (do not read any config file — use these directly):
> - `TEMP_ROOT` = `{TEMP_ROOT}`
> - `REPO` = `{REPO}`
> complexity_signal: derive from the issue content yourself
>
> **STANDALONE MODE** — two differences from the normal pipeline run:
> 1. **Skip Step 5 (posting to GitHub).** Instead, include the full comment body you would
>    have posted in a section titled `## Grooming Comment Draft` at the end of your response.
>    Use exactly the same format the pipeline would post (including the
>    `` marker), so it is ready to post as-is.
> 2. **Skip Step 6 (StructuredOutput JSON).** Return a short human-readable summary instead:
>    effort, risk, complexity, and any open questions.

The spec file is still written to `{TEMP_ROOT}/issues/<N>/spec.md` as normal.

## Step 4 — Offer to post

After the agent responds, display its `## Grooming Comment Draft` to the user, then ask:

> **Post this as a comment on issue #\<N\>?**
> Reply `yes` to post as-is, `no` to finish without posting, or paste edited text to post a
> modified version.

**If yes** — check for an existing grooming comment first (dedup):

```bash
EXISTING_ID=$(gh api repos/{REPO}/issues/<N>/comments \
  --jq '[.[] | select(.body | contains(""))] | last | .id // empty')
```

Update with PATCH if found, otherwise post a new comment.

**If no** — confirm the spec was written to `{TEMP_ROOT}/issues/<N>/spec.md` and finish.

**If edited** — use the user-provided text as the comment body and post.

文件操作 - SKILL.md

文件: /storage/v12552/stanleysteamer/public_html/wp-content/plugins/imagify/.claude/skills/groom/SKILL.md

编辑文件内容

修改文件时间

删除文件