Source profileQuality 72/100

dyoshikawa/rulesync/.rulesync/skills/create-issue/SKILL.md

create-issue

Create a GitHub issue with detailed description, purpose, and appropriate labels

Source repository stars
1,263
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Create a GitHub issue with detailed description, purpose, and appropriate labels

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/create-issue"
    Safe inspection promptEditorial

    Inspect the Agent Skill "create-issue" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/create-issue/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Step 1: Gather Information

      Receive the issue topic from $ARGUMENTS or the user's description.

      What needs to be done (the task or problem)Why it needs to be done (the purpose or motivation)Receive the issue topic from $ARGUMENTS or the user's description.
    2. 02

      Step 2: Research Context

      Before writing the issue, investigate the relevant parts of the codebase to understand:

      Which files and modules are affectedExisting related code patternsPotential impact and scope of the change
    3. 03

      Step 3: Draft the Issue

      Important: All issue content (title, body, labels) must be written in English, regardless of the language used in the conversation with the user.

      Important: All issue content (title, body, labels) must be written in English, regardless of the language used in the conversation with the user.Create a well-structured issue with the following sections:
    4. 04

      Step 4: Assign Labels

      First, get the available labels from the repository:

      First, get the available labels from the repository:Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-d…

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score72/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars1,263SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    dyoshikawa/rulesync
    Skill path
    .rulesync/skills/create-issue/SKILL.md
    Commit
    310b711fbe8cffc14debb276ade8a384c2b89083
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Create GitHub Issue

    Step 1: Gather Information

    Receive the issue topic from $ARGUMENTS or the user's description.

    If the information is insufficient, ask the user to clarify the following:

    • What needs to be done (the task or problem)
    • Why it needs to be done (the purpose or motivation)

    Step 2: Research Context

    Before writing the issue, investigate the relevant parts of the codebase to understand:

    • Which files and modules are affected
    • Existing related code patterns
    • Potential impact and scope of the change

    Step 3: Draft the Issue

    Important: All issue content (title, body, labels) must be written in English, regardless of the language used in the conversation with the user.

    Create a well-structured issue with the following sections:

    ## Summary
    
    A concise one-liner describing what this issue is about.
    
    ## Motivation / Purpose
    
    Why this change is needed. Explain the problem, user impact, or improvement opportunity.
    
    ## Details
    
    Detailed description of what needs to be done:
    
    - Specific changes required
    - Files or modules likely affected
    - Acceptance criteria or expected behavior
    
    ## Additional Context
    
    Any relevant links, screenshots, or references (if applicable).
    

    Step 4: Assign Labels

    First, get the available labels from the repository:

    gh label list
    

    Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the good first issue label if it exists in the repository.

    Step 5: Create the Issue

    gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
    

    Step 6: Report Result

    Output the created issue URL and a summary of:

    • Issue title
    • Assigned labels
    • Whether good first issue was applied and why (or why not)

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Computed 10042,015

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    Computed 9831,966

    K-Dense-AI/scientific-agent-skills

    dask

    Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.