agentleFS
Sign inStart free
finosfinos/git-proxy/.agents/skills/issue/SKILL.md

issue

Skill262 starsChanged 2 months agoApache-2.0View on GitHub

Create a GitHub issue markdown file from a bug report, feature request, or discussion context

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a GitHub issue markdown file from the details provided by the user.

    line 6
  2. Distinctive:

    Read AGENTS.md first. It is the canonical project guide for this repository.

    line 8
  3. Distinctive:

    Read the user's input to understand the problem, who reported it, and any logs or reproduction steps provided

    line 14
  4. Very specific:

    Write a concise GitHub issue markdown file and save it to plans/issue-<short-slug>.md

    line 16
  5. Very specific:

    Start with ## <title> as the first line (this becomes the GitHub issue title)

    line 20
  6. Distinctive:

    Keep it concise — the whole issue should be under 80 lines

    line 31
  7. Distinctive:

    Use code blocks sparingly — only for key log lines and small code snippets

    line 32
  8. Distinctive:

    Do not propose fixes or implementation approaches

    line 33
  9. Very specific:

    Do not add Labels, Description, or Title as separate sections — the ## heading is the title

    line 34
  10. Distinctive:

    Write for a contributor who knows the project but hasn't seen this specific bug

    line 35

“Common” is measured: kept by at least 6 in 10 of the 44 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

Create a GitHub issue markdown file from the details provided by the user.

Read AGENTS.md first. It is the canonical project guide for this repository.

The user will describe a bug, feature request, or discussion context (e.g. Slack conversations, error logs, reproduction steps). Your job is to turn that into a well-structured issue and save it to plans/.

Steps:

  1. Read the user's input to understand the problem, who reported it, and any logs or reproduction steps provided
  2. Investigate the codebase to identify relevant code paths, pinpoint where the issue likely originates, and gather context that would help a contributor understand the problem
  3. Write a concise GitHub issue markdown file and save it to plans/issue-<short-slug>.md

Issue format:

  • Start with ## <title> as the first line (this becomes the GitHub issue title)
  • ### Problem — 2-3 sentences explaining the issue and its impact
  • ### Steps to Reproduce — numbered list (if applicable)
  • ### Expected Behavior — 1-2 sentences
  • ### Actual Behavior — include relevant log snippets in code blocks, keep them short (trim stack traces to the key lines)
  • ### Potential Root Cause — based on your codebase investigation, explain where the issue likely lives. Link to source code using upstream GitHub URLs: https://github.com/finos/git-proxy/blob/main/...#L<start>-L<end>.
  • ### Affected Files — table with file links and one-line role descriptions
  • ### Additional Context — bullet points for version info, related code paths, or anything else useful

Style rules:

  • Keep it concise — the whole issue should be under 80 lines
  • Use code blocks sparingly — only for key log lines and small code snippets
  • Do not propose fixes or implementation approaches
  • Do not add Labels, Description, or Title as separate sections — the ## heading is the title
  • Write for a contributor who knows the project but hasn't seen this specific bug
  • No emojis

$ARGUMENTS

Download now (ZIP)

  • Other versions46 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 46

    1. remotion-dev/remotion★ 70ksame name
    2. tldraw/tldraw★ 51ksame name
    3. tokio-rs/toasty★ 3.3ksame name
    4. dataplat/dbatools★ 2.9ksame name
    5. aws/graph-explorer★ 489same name
    6. egregore-labs/egregore★ 293same name
    7. alamenai/terrae★ 245same name
    8. awslabs/loom★ 200same name
    9. dedalus-labs/wingman★ 181same name
    10. team-attention/hoyeon★ 173same name

    36 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use branch, browse and 6 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.
    • MindgamesSkill

      branch

      Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

      Also in 3 projects that use this

    • CodeWithBehnamSkill

      browse

      Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence.

      Also in 3 projects that use this

    • vertz-devSkill

      backlog

      Manages deferred/blocked work items as GitHub Issues with labels and blocker tracking

      Also in 3 projects that use this

    • Microsoft AzureSkill

      test

      Also in 7 projects that use this

    • lukeleekrSkill

      scout

      GitHub 레포 스카우터. 내 Claude Code + Codex App 환경을 분석하여 필요한 GitHub 레포를 자동 추천하거나, 키워드로 GitHub을 검색합니다. "scout", "스카우트", "깃헙 탐방", "레포 추천", "repo search" 등의 키워드에 반응합니다.

      Also in 3 projects that use this

    • VercelSkill

      deploy

      Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

      Also in 4 projects that use this

  • In this repository10 other files it gives its agents.

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.

Check your setup, free