[GH-ISSUE #19] Add meta-command for post-failure command improvement workflow #3

New issue

Open

opened 2026-10-26 22:06:41 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-26 22:06:41 +00:00

Owner

Originally created by @benceruleanlu on GitHub (Jul 6, 2025).
Original GitHub issue: https://github.com/Comfy-Org/comfy-claude-prompt-library/issues/19

Currently, when a command doesn't perform as expected due to
edge cases (e.g., checking if on a feature branch but not the
correct feature branch), there's no streamlined workflow to
capture these learnings and improve the command immediately.

Example scenario: The PR-submit-local-as-new-pr.md command
initially only checked if the user was on a feature branch, but
didn't validate if it was semantically appropriate for the
changes being made. This led to PRs including unrelated commits.

Proposed solution: Create a new command like
/development:improve-command-after-failure that:

Captures the failure context and resolution
Updates the command with the fix OR
Documents which alternative command should have been used
Optionally creates a "lessons learned" entry

This would enable rapid iteration on commands based on
real-world usage patterns and edge cases.

(yes my github pat 403ed for issue creation, i'm fixing it)

Originally created by @benceruleanlu on GitHub (Jul 6, 2025). Original GitHub issue: https://github.com/Comfy-Org/comfy-claude-prompt-library/issues/19 Currently, when a command doesn't perform as expected due to edge cases (e.g., checking if on a feature branch but not the correct feature branch), there's no streamlined workflow to capture these learnings and improve the command immediately. Example scenario: The PR-submit-local-as-new-pr.md command initially only checked if the user was on a feature branch, but didn't validate if it was semantically appropriate for the changes being made. This led to PRs including unrelated commits. Proposed solution: Create a new command like /development:improve-command-after-failure that: 1. Captures the failure context and resolution 2. Updates the command with the fix OR 3. Documents which alternative command should have been used 4. Optionally creates a "lessons learned" entry This would enable rapid iteration on commands based on real-world usage patterns and edge cases. (yes my github pat 403ed for issue creation, i'm fixing it)

bsakaguchi commented

2026-10-26 22:06:42 +00:00

Author

Owner

@christian-byrne commented on GitHub (Jul 6, 2025):

That's really smart, great idea. Anything that lets us iterate on the CC tooling over time is money.

@christian-byrne commented on GitHub (Jul 6, 2025): That's really smart, great idea. Anything that lets us iterate on the CC tooling over time is money.

bsakaguchi commented

2026-10-26 22:06:43 +00:00

Author

Owner

@christian-byrne commented on GitHub (Jul 6, 2025):

By the way, whenever I am using CC to help adjust any CC tooling, I start with this command github.com/Comfy-Org/comfy-claude-prompt-library@736336dca6/.claude/commands/agents/AGENT-learn-claude-code-best-practices.md (L4) to give good context

@christian-byrne commented on GitHub (Jul 6, 2025): By the way, whenever I am using CC to help adjust any CC tooling, I start with this command https://github.com/Comfy-Org/comfy-claude-prompt-library/blob/736336dca657144d16cfd6b8841b2b89f58010b6/.claude/commands/agents/AGENT-learn-claude-code-best-practices.md#L4 to give good context

bsakaguchi referenced this issue

2026-10-26 22:06:48 +00:00

[PR #3] [MERGED] [docs] Add contributing guidelines #6