agentleFS
Sign inStart free
ElasticKnown publisherelastic/docs-builder/.claude/skills/issue/SKILL.md

issue

Skill25 starsChanged 19 days agoApache-2.0View on GitHub

File a well-formed bug report or feature request. Use when the user asks to open an issue, report a bug, or request a feature in the docs-builder repo.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read .claude/skills/writing-style.md and .claude/skills/surfaces.md before writing anything.

    line 8
  2. Very specific:

    Search for near-duplicates before opening anything.

    line 16
  3. Distinctive:

    Always print the URL so the user can open it directly.

    line 119

“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

Issue Skill

Read .claude/skills/writing-style.md and .claude/skills/surfaces.md before writing anything.

Files a GitHub issue that matches the repo's templates, applies correct labels, and checks for duplicates first.

Steps

1. Check for duplicates

Search for near-duplicates before opening anything. Link any you find in the issue body rather than filing a second. Use the full URL form for all links — see ## Linking to issues and pull requests in writing-style.md.

gh issue list --search "<key terms>" --limit 10

2. Determine the issue type

  • Bug — something that used to work stopped, or produces wrong output. Use bug-report structure.
  • Feature / enhancement — something that does not exist yet, or needs to be better. Use enhancement structure.

3. Write the title

  • ≤70 characters, no trailing period
  • States the observable problem or the wanted capability — not the internal cause or the implementation

4. Write the body

Bug report:

<One sentence: what went wrong and, briefly, under what condition. Be specific.>

### What happened

<What you saw. Include the command you ran, the input, and the exact output or
 error. Commands and error messages go in fenced blocks.>

### How to reproduce

<Minimal steps. A command and the file it ran against is enough if that covers it.
 Skip this section if the "What happened" section already makes it reproducible.>

### Version or commit

<Output of `docs-builder --version`, or the commit SHA if building from source.
 This is the single most useful piece of triage data.>

Feature request:

<One sentence: the outcome you want, not the implementation.>

### What is getting in your way

<The concrete limitation. What are you trying to do, and what stops you?
 One to three sentences.>

### What would you like instead

<Your proposed change or outcome. If you have a specific implementation in mind,
 describe it — but a clear outcome is enough.>

### Anything else

<Examples from other tools, links, screenshots, or context that did not fit above.
 Skip this section if there is nothing to add.>

Formatting rules:

  • Same plain-language rules as PR bodies — active voice, short sentences, no mechanical noun clusters.
  • Commands and error messages in fenced blocks.
  • Backticks on all identifiers: flags, config keys, file paths, method names.
  • Skip any section that has nothing to say — a blank section adds noise, not structure.

5. Choose labels

File with two or three labels:

  1. Type (required, from the template): bug or enhancement
  2. Area (one, if it fits): derived from the surface map in surfaces.md. Pick from the repo's existing area labels — do not invent new ones: authoring · links · tables · attributes · versioning · build · automation · migration · SEO · user-experience · tech-debt · design
  3. needs triage (always)

These are issue labels, not release-drafter PR labels. Do not use feature, chore, redesign, changelog:skip, etc. here.

6. Create the issue

One call — title, labels, and body together:

gh issue create \
  --title "<title>" \
  --label "bug,<area-label>,needs triage" \
  --body "$(cat <<'EOF'
<lead sentence>

### What happened

...

### Version or commit

...
EOF
)"

Replace bug with enhancement for feature requests. Omit the area label if none fits — do not force one.

7. Return the issue URL

Always print the URL so the user can open it directly.

Download now (ZIP)

  • Other versions46 projects use a version of this.

    Word for word · 0

    None found.

    Wrote their own version · 41

    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. finos/git-proxy★ 262same name
    8. alamenai/terrae★ 245same name
    9. awslabs/loom★ 200same name
    10. dedalus-labs/wingman★ 181same name

    31 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 7 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

    • 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

    • kt057Skill

      check

      lint, typecheck, test を一括実行して結果をサマリーする

      Also in 3 projects that use this

  • In this repository12 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