Rename directories: coding-context → prompts, prompts/ → tasks/

[Copilot]

Renamed the parent .coding-context directory to .prompts and the prompts/ subdirectory to tasks/.

Changes

Directory structure:

-.coding-context/
-├── prompts/          # Task-specific prompt templates
+.prompts/
+├── tasks/            # Task-specific prompt templates
 │   └── <task-name>.md
 └── memories/         # Reusable context files
     └── *.md

Default search paths:

• .coding-context → .prompts
• ~/.config/coding-context → ~/.config/prompts
• /var/local/coding-context → /var/local/prompts

Task file lookup:

• {dir}/prompts/{task}.md → {dir}/tasks/{task}.md

All documentation, examples, and tests updated accordingly.

Real-World Task Examples

Added comprehensive task examples demonstrating common development workflows:

• implement-jira-story - Template for implementing features from Jira stories with acceptance criteria and jira-cli commands
• triage-jira-bug - Template for investigating and triaging bugs with root cause analysis using jira-cli
• respond-to-jira-comment - Template for responding to comments on Jira issues with jira-cli integration
• review-pull-request - Template for conducting thorough code reviews with checklists
• respond-to-pull-request-comment - Template for addressing reviewer feedback on PRs
• fix-failing-check - Template for debugging and fixing failing CI/CD checks

Each example includes YAML frontmatter, template parameters, detailed instructions, and usage examples.

Jira-CLI Integration

The Jira task examples now integrate with kitproj/jira-cli and include exact commands:

• jira get-issue <issue-key> - Retrieve issue details
• jira get-comments <issue-key> - Get all comments on an issue
• jira add-comment <issue-key> "comment" - Add a comment to an issue
• jira update-issue-status <issue-key> "status" - Update issue workflow status (e.g., "In Progress", "In Review", "Done")

These commands are embedded in the task templates with template parameter substitution support.

Original prompt

Change the current "prompts" directory to be named "tasks and the "coding-context" directories to be named "prompts".

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[alexec]

@copilot I'd like to add some examples of tasks:

• implement-jira-story
• triage-jira-bug
• responsd-to-jira-comment
• review-pull-request
• respond-to-pull-request-comment
• fix-failing-check

Include some example prompts.

[Copilot]

@copilot I'd like to add some examples of tasks:

• implement-jira-story
  ...

Added all six task examples with comprehensive prompts in commit a01fc24. Each example includes:

• Template structure with frontmatter and parameters
• Detailed instructions and checklists
• Usage examples with parameter values

The examples cover: implement-jira-story, triage-jira-bug, respond-to-jira-comment, review-pull-request, respond-to-pull-request-comment, and fix-failing-check.

[alexec]

@copilot look the kitproj/jira-cli repo. Update the Jira example to use that tool. Include the exact commands to execute in the prompt.

[Copilot]

@copilot look the kitproj/jira-cli repo. Update the Jira example to use that tool. Include the exact commands to execute in the prompt.

Updated all three Jira task examples in commit 2b4892a to use the jira-cli tool. Each example now includes exact commands:

implement-jira-story:

• jira get-issue {{ .storyId }}
• jira get-comments {{ .storyId }}
• jira add-comment {{ .storyId }} "..."
• jira update-issue-status {{ .storyId }} "In Progress"/"In Review"/"Done"

triage-jira-bug:

• jira get-issue {{ .bugId }}
• jira get-comments {{ .bugId }}
• jira add-comment {{ .bugId }} "..." (for triage updates)
• jira update-issue-status {{ .bugId }} "In Progress"

respond-to-jira-comment:

• jira get-issue {{ .issueId }}
• jira get-comments {{ .issueId }}
• jira add-comment {{ .issueId }} "..." (for posting response)
• jira update-issue-status {{ .issueId }} "..."

All commands use template variables so they work with the coding-context CLI parameter substitution.