Conversation
- Remove "detailed" qualifier from issue creation instructions - Add explicit backend type indicators to prompts - Simplify command reference phrasing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR refactors the issue creation prompts in the DevAIFlow CLI to clarify backend type instructions. The changes improve user experience by making the prompts in
git newandjira newcommands less confusing when creating tickets.The refactoring focuses on clarifying the backend type selection process during ticket creation sessions, making it more intuitive for users to understand which backend they're working with.
Assisted-by: Claude
Testing
Steps to test
devflow git newcommand and verify the prompts clearly indicate the backend typedevflow jira newcommand and verify the prompts clearly indicate the backend typeScenarios tested
Deployment considerations