From 9ee7477a943992b72288acccef4e4117e529eea3 Mon Sep 17 00:00:00 2001 From: Sachin Iyer Date: Thu, 7 May 2026 18:15:46 -0700 Subject: [PATCH] fix(skills): drop $ARGUMENTS templating from detail-bugs and detail-create-rules When invoked with prose, Claude Code interpolates the full sentence into $ARGUMENTS and the CLI rejects it as a malformed owner/repo. The CLI already infers the repo from the git remote; if a different repo is needed, Claude can pass an explicit flag instead of relying on skill templating. Co-Authored-By: Claude Opus 4.7 (1M context) --- .claude/skills/detail-bugs/SKILL.md | 13 ++++--------- .claude/skills/detail-create-rules/SKILL.md | 11 +++-------- 2 files changed, 7 insertions(+), 17 deletions(-) diff --git a/.claude/skills/detail-bugs/SKILL.md b/.claude/skills/detail-bugs/SKILL.md index 53159df..6458c06 100644 --- a/.claude/skills/detail-bugs/SKILL.md +++ b/.claude/skills/detail-bugs/SKILL.md @@ -1,7 +1,6 @@ --- name: detail-bugs description: Fetch Detail bugs for a repository. List pending bugs, show details for each, fix the bugs, and mark them as resolved or dismissed. -argument-hint: --- # Fetch Detail Bugs @@ -10,11 +9,7 @@ Get bugs from Detail for a repository and help the user triage them. ## Determining the Repository -If `$ARGUMENTS` is not empty, use it as the repository (`owner/repo`) for all `detail bugs` commands. - -Otherwise, the Detail CLI will infer the repository from the git remote. Use the CLI with no repository specified. - -If commands fail to infer the repository, ask the user to provide the repository and use it for the `detail bugs` commands. +The Detail CLI infers the repository from the git remote; if the user specifies a different repo, pass it explicitly to the CLI commands. ## Prerequisites @@ -30,14 +25,14 @@ The user must be authenticated. Assume that the user is authed and run commands To scope bugs to a particular scan, first get the scan's workflow request ID: ```bash -detail scans list $ARGUMENTS +detail scans list ``` The output includes a `Workflow ID` column (values like `wr_...`). Then pass that ID to `bugs list`: ```bash -detail bugs list $ARGUMENTS --scan-id +detail bugs list --scan-id ``` This returns only bugs found in that scan, still filtered by `--status` @@ -46,7 +41,7 @@ closed bugs for the scan. ## Step 1: List pending bugs -Run `detail bugs list $ARGUMENTS` to fetch all pending bugs. +Run `detail bugs list` to fetch all pending bugs. Present the list to the user and ask which bug they want to look at first, or offer to go through them in order. diff --git a/.claude/skills/detail-create-rules/SKILL.md b/.claude/skills/detail-create-rules/SKILL.md index fa2f817..d430549 100644 --- a/.claude/skills/detail-create-rules/SKILL.md +++ b/.claude/skills/detail-create-rules/SKILL.md @@ -1,7 +1,6 @@ --- name: detail-create-rules description: Interactively create a new Detail rule for a repository — gather context, submit the creation request, wait for completion, review the results, and pull them locally. Use when asked to "create a rule", "add a rule", "propose rules", "create/propose a Detail rule", or similar. -argument-hint: --- # Create a Detail Rule @@ -10,11 +9,7 @@ Guide the user through creating one or more new rules for their repository. ## Determining the Repository -If `$ARGUMENTS` is not empty, use it as the repository (`owner/repo`) for all `detail rules` commands. - -Otherwise, the Detail CLI will infer the repository from the git remote. Use the CLI with no repository specified. - -If commands fail to infer the repository, ask the user to provide the repository and use it for the `detail rules` commands. +The Detail CLI infers the repository from the git remote; if the user specifies a different repo, pass it explicitly to the CLI commands. ## Prerequisites @@ -36,12 +31,12 @@ Ask the user what they want to do: **For a specific rule**, build the command from whatever context the user provided. At least one of `--description`, `--bug-ids`, or `--commit-shas` is required: ```bash -detail rules create $ARGUMENTS [--description ""] [--bug-ids ] [--commit-shas ] +detail rules create [--description ""] [--bug-ids ] [--commit-shas ] ``` **For AI-proposed rules**: ```bash -detail rules propose $ARGUMENTS +detail rules propose ``` Both commands return a request ID (`rcr_...`). Save it — you will need it to poll for status.