GitHub Issue Tracker

Purpose

Streamline your development workflow by converting conversations, ideas, and tasks into well-structured GitHub issues. This skill helps you capture requirements, track bugs, and manage feature requests directly from your Basile workspace.

When to Use

Use this Skill when you need to:

• Create GitHub issues from meeting notes or discussions
• Track bugs discovered during conversations
• Convert feature ideas into actionable issues
• Organize project tasks across repositories
• Document technical requirements as issues

Step-by-Step Process

Step 1: Identify the Task or Issue

Understand what needs to be tracked in GitHub.

Help the user clarify what they want to create:

Ask guiding questions:

• "What do you want to create an issue for? (bug, feature, task, documentation)"
• "Can you describe the issue or task in detail?"
• "What repository should this go in?"
• "What is the priority or urgency?"

Context to gather:

• Issue type (bug, feature, enhancement, documentation, chore)
• Detailed description
• Repository name
• Priority level
• Any related issues or context

Output Variable: issue_context

Step 2: Select Repository

Choose the target GitHub repository.

Use GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER to show available repositories.

Help the user select:

• List their repositories with descriptions
• Confirm the selected repository
• Verify write access if needed

Output Variable: selected_repository

Step 3: Draft Issue Content

Create a well-structured issue with title, description, and metadata.

Based on the context gathered, draft:

Title: Clear, concise summary (imperative mood for tasks, descriptive for bugs)

Body:

• Problem statement or feature description
• Steps to reproduce (for bugs)
• Acceptance criteria (for features)
• Technical notes or constraints
• Related links or references

Labels: Suggest appropriate labels based on issue type:

• bug, feature, enhancement, documentation
• priority: high, medium, low
• good first issue (if applicable)

Show the draft to user for approval before creating.

Output Variable: issue_draft

Step 4: Create GitHub Issue

Create the issue in the selected repository.

Use GITHUB_CREATE_AN_ISSUE to create the issue with:

• Title from draft
• Body from draft
• Repository from selection

Then optionally:

• Use GITHUB_ADD_LABELS_TO_AN_ISSUE if labels were specified
• Use GITHUB_ADD_ASSIGNEES_TO_AN_ISSUE if assignees were specified

Output Variable: created_issue

Step 5: Document and Confirm

Save a record and provide the issue link.

Create a document with:

• Issue title and number
• Repository link
• Issue URL
• Summary of what was created
• Next steps or follow-up items

Use basile_create_document to save if requested.

Provide:

• Direct link to the created issue
• Confirmation of labels and assignees
• Suggestions for related issues to create

Output Variable: issue_summary

Best Practices

• Write clear, actionable issue titles
• Include reproduction steps for bugs
• Add acceptance criteria for features
• Use labels consistently
• Link related issues when relevant