agentleFS
TabbyMLTabbyML/pochi/.agents/skills/create-issue/SKILL.md

create-issue

Skill127 starsChanged 4 days agoApache-2.0View on GitHub

Help create a github issue given the request

66 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use native-nostalgia-stack, software-engineering-excellence and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • frostneySkill

    software-engineering-excellence

    Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.

    Also in 3 projects that use this

  • withpiperSkill

    roadmap-review

    Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.

    Also in 3 projects that use this

  • GoogleSkill

    implement-issue

    Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    create-release

    Use when creating a new ASO release, including pre-checks, release notes generation, draft GitHub release creation, documentation updates, and ROADMAP changes.

    Also in 4 projects that use this

  • MicrosoftSkill

    update-pr

    Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create an issue in the TabbyML/pochi repository.

    line 9
  2. Very specific:

    Title Formatting: Do NOT use PR or commit semantics for issue titles (e.g., avoid prefixes like feat(cli): or fix(vscode-webui):).

    line 10
  3. Very specific:

    When creating issue, attach following information in footer of issue.

    line 11
  4. Very specific:

    After creating the issue, please assign it to project "Pochi Tasks" and add appropriate labels (see existing issues for reference) Example …

    line 15
  5. Distinctive:

    If the user specifies an Assignee, Priority (e.g., P1, P2), or Release (e.g., v0.42), update those as well:

    line 20
  6. Very specific:

    Update the field: gh project item-edit --id <item-id> --field-id <field-id> --project-id <project-id> --single-select-option-id <option-id>

    line 29
  7. Very specific:

    If gh issue edit failed to add project, should ask user to refresh their gh token to authorize it with the project scope (gh auth refresh …

    line 30

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Github Issue Creator

  1. Please conduct a thorough search of the codebase on relevant code snippets to help implement the feature / debug the issue.
  2. Create an issue in the TabbyML/pochi repository. Select the appropriate template from .github/ISSUE_TEMPLATE and use gh cli to create the issue.
    • Title Formatting: Do NOT use PR or commit semantics for issue titles (e.g., avoid prefixes like feat(cli): or fix(vscode-webui):). Instead, use clear, descriptive sentence-case titles (e.g., Support fork-agent in CLI).
  3. When creating issue, attach following information in footer of issue. 🤖 Generated with Pochi
  4. Please include as much as possible information about the issues, especially link to existing code (make sure you make the link clickable by prefixing them with github link)
  5. Be respectful and considerate in your issue description and comments, make it concise and clear.
  6. After creating the issue, please assign it to project "Pochi Tasks" and add appropriate labels (see existing issues for reference) Example commands:
    gh issue edit <issue-number> --add-project "Pochi Tasks"
  7. If the user specifies an Assignee, Priority (e.g., P1, P2), or Release (e.g., v0.42), update those as well:
    • Add Assignee: gh issue edit <issue-number> --add-assignee <username>
    • To update project fields (Priority, Release), you must find the relevant IDs and update the project item:
      1. Get Project Number/ID: gh project list --owner TabbyML
      2. Get Field and Option IDs: gh project field-list <project-number> --owner TabbyML --format json
      3. Get Project Item ID for the issue:
        gh project item-list <project-number> --owner TabbyML --format json | jq -r '.items[] | select(.content.number == <issue-number>) | .id'
      4. Update the field: gh project item-edit --id <item-id> --field-id <field-id> --project-id <project-id> --single-select-option-id <option-id>
  8. If gh issue edit failed to add project, should ask user to refresh their gh token to authorize it with the project scope (gh auth refresh -s project).

IMPORTANT: You only need to create the issue, DO NOT attempt to fix the issue or implement the feature.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.