القائمة
Use this skill when asked to create a GitHub issue. It handles different issue types (bug, feature, etc.) using repository templates and ensures proper labeling.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | github-issue-creator |
| description | Use this skill when asked to create a GitHub issue. It handles different issue types (bug, feature, etc.) using repository templates and ensures proper labeling. |
This skill guides the creation of high-quality GitHub issues that adhere to the repository's standards and use the appropriate templates.
Follow these steps to create a GitHub issue:
Identify Issue Type: Determine if the request is a bug report, feature request, or other category.
Locate Template: Search for issue templates in
.github/ISSUE_TEMPLATE/.
bug_report.ymlfeature_request.ymlwebsite_issue.yml.md templates in the same
directory.Read Template: Read the content of the identified template file to understand the required fields.
Draft Content: Draft the issue title and body/fields.
id defined in
the template.🔒 maintainer only label unless the
user explicitly requests otherwise.Create Issue: Use the gh CLI to create the issue.
For Markdown Templates or Simple Body:
# 1. Write the drafted content to a temporary file
# 2. Create the issue using the --body-file flag
gh issue create --title "Succinct title" --body-file <temp_file_path> --label "🔒 maintainer only"
# 3. Remove the temporary file
rm <temp_file_path>
For YAML Templates (Forms):
While gh issue create supports --body-file, YAML forms usually expect
key-value pairs via flags if you want to bypass the interactive prompt.
However, the most reliable non-interactive way to ensure formatting is
preserved for long text fields is to use the --body or --body-file if the
form has been converted to a standard body, OR to use the --field flags
for YAML forms.
Note: For the jiminy-cli repository which uses YAML forms, you can often
submit the content as a single body if a specific field-based submission is
not required by the automation.
Verify: Confirm the issue was created successfully and provide the link to the user.
--body-file to
prevent newline and special character issues.Trigger this skill when the user wants to start an asynchronous PR review, run background checks on a PR, or check the status of a previously started async PR review.
Guidance for creating, running, fixing, and promoting behavioral evaluations. Use when verifying agent decision logic, debugging failures, debugging prompt steering, or adding workspace regression tests.
A specialized skill for Jiminy CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.
Generates and formats changelog files for a new release based on provided version and raw changelog data.
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Jiminy CLI. Requires `gh` CLI tool.