Menu
File a bug report or feature request to a project's GitHub repository
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Conduct thorough code reviews for pull requests and pre-commit changes
Run comprehensive project health checks including code quality, documentation, git status, and project structure
Check CI/CD workflow status and troubleshoot failing checks in GitHub Actions
Initialize .docent/ directory structure and configuration for a new project
Comprehensive guide for AI agents on proactive documentation capture using /docent:tell
Migrate a docent v0.9 project to v1.0 skills-based architecture
| name | file-issue |
| description | File a bug report or feature request to a project's GitHub repository |
| group | github |
| keywords | ["github","issues","bug report","feature request","bug","feature","filing issues"] |
| version | 1.0.0 |
| author | docent |
This runbook files bug reports, feature requests, questions, or documentation issues to a project's GitHub repository using the gh CLI.
Standardize issue creation with proper formatting, required information, and appropriate labels. Works with any project configured in .docent/config.yaml.
gh CLI installed and authenticated (gh auth status).docent/config.yaml with repository informationThis runbook accepts the following variables:
Additional type-specific variables:
For bugs:
For features:
For documentation:
Action: Determine which GitHub repository to file against
From .docent/config.yaml:
projects:
docent:
repo: tnez/docent
my-app:
repo: user/my-app
Resolution logic:
project variable provided → use that project's repoproject = "current" or not provided → detect from git remoteCommands:
# Get current repo from git remote
git remote get-url origin | sed 's/.*github.com[:/]\(.*\)\.git/\1/'
# Validate repo exists
gh repo view <owner/repo> --json name
Validation:
owner/repo formatAction: Generate appropriate issue template based on type
## Description
{{description}}
## Current Behavior
{{actual_behavior}}
## Expected Behavior
{{expected_behavior}}
## Steps to Reproduce
{{reproduction_steps}}
## Environment
- OS: {{os}}
- Version: {{version}}
---
Filed via [docent](https://github.com/tnez/docent)
## Feature Description
{{description}}
## Use Case
{{use_case}}
## Suggested Solution
{{suggested_solution}}
---
Filed via [docent](https://github.com/tnez/docent)
## Question
{{description}}
---
Filed via [docent](https://github.com/tnez/docent)
## Documentation Issue
{{description}}
## Location
{{location}}
## Suggested Improvement
{{suggestion}}
---
Filed via [docent](https://github.com/tnez/docent)
Action: Determine labels based on issue type
Label mapping:
bugenhancement, feature-requestquestiondocumentationAdditional labels (if detectable):
mcp, templates, documentation)priority: high if certain keywords present)Commands:
# Check available labels for repository
gh label list --repo <owner/repo>
Action: File the issue using gh issue create
Commands:
# Create issue with body from file
gh issue create \
--repo <owner/repo> \
--title "<title>" \
--body "<formatted body>" \
--label "<labels>"
# Example for bug:
gh issue create \
--repo tnez/docent \
--title "Bootstrap fails with permission error" \
--body "$(cat issue-body.md)" \
--label "bug"
Validation:
Action: Provide confirmation with issue link
Success Message:
✅ Issue filed successfully!
Issue #123: <title>
URL: https://github.com/<owner/repo>/issues/123
The issue has been created with:
- Type: <type>
- Labels: <labels>
- Status: Open
You can view and track the issue at the URL above.
Additional actions:
.docent/journals/ for trackingInvocation:
/docent:act file issue in docent: bootstrap fails on Windows with permission error
(Agent interprets and extracts):
- project: docent
- type: bug
- title: "Bootstrap fails on Windows with permission error"
- description: "When running bootstrap on Windows, permission denied error occurs"
Generated issue:
Invocation:
/docent:act file feature request: add dark mode support
(Agent interprets):
- project: current (detected from git remote)
- type: feature
- title: "Add dark mode support"
- use_case: Better UX for users working at night
Generated issue:
Invocation:
/docent:act file documentation issue for docent: getting started guide is outdated
(Agent interprets):
- project: docent
- type: documentation
- title: "Getting started guide is outdated"
- location: docs/guides/getting-started.md
Generated issue:
Symptoms: gh issue create fails with authentication error
Fix:
# Authenticate with GitHub
gh auth login
# Follow prompts to authenticate
Validation: gh auth status shows authenticated
Symptoms: Cannot find repository from config or git remote
Fix:
.docent/config.yaml has correct repogit remote get-url originSymptoms: Cannot create issues in repository
Fix:
gh auth refresh to update permissionsSymptoms: Cannot reach GitHub
Fix:
Add projects to .docent/config.yaml:
projects:
docent:
repo: tnez/docent
default_labels:
- via-docent
my-app:
repo: user/my-app
default_labels:
- automated
work-project:
repo: company/project
default_labels:
- from-docent
- needs-triage
Options:
repo: GitHub repository in owner/repo format (required)default_labels: Labels to add to all issues (optional)After filing issue:
File multiple related issues:
/docent:act file issues for planned features:
1. Add export functionality
2. Implement search
3. Create user dashboard
Agent can interpret and file 3 separate feature requests
Projects can define custom templates in .docent/templates/issue-*.md that override default formats
Configure intelligent labeling based on content:
projects:
my-app:
repo: user/my-app
auto_labels:
- pattern: "auth|login|password"
labels: ["area: auth"]
- pattern: "slow|performance|speed"
labels: ["performance"]
health-check - Find issues to file before they become bugscode-review - Review changes before filing improvement issues