agentleFS
dedalus-labsdedalus-labs/wingman/.agents/skills/issue/SKILL.md

issue

Skill181 starsChanged 7 months agoMITView on GitHub

Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use branch, backlog and 9 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

  • vertz-devSkill

    backlog

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

    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

  • Microsoft AzureSkill

    test

    Also in 7 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 4 projects that use this

  • lukeleekrSkill

    scout

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

    Also in 3 projects that use this

  • +1 more from Azure

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 0

    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 the matching template file from .github/ISSUE_TEMPLATE/.

    line 44
  2. Very specific:

    Run gh issue create with the right labels.

    line 48

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

Context (auto-detected from HEAD)

  • Current branch: !git branch --show-current
  • Last commit: !git log -1 --oneline
  • Remote: !git remote get-url origin

Template Selection

Parse the first positional arg from $ARGUMENTS as the issue type:

TypeTemplate fileLabels
bug.github/ISSUE_TEMPLATE/bug_report.ymlbug,triage
feature.github/ISSUE_TEMPLATE/feature_request.ymlenhancement

The bug_report.yml file is a GitHub issue form. gh issue create --body submits plain markdown, so translate the yaml form fields into a markdown body with the same section headings (Bug Description, Steps to Reproduce, Expected Behavior, Environment, Additional Context).

For feature_request.yml, read the file and translate form fields the same way.

Rules

  • Issue title: short, imperative, no period, under 80 chars. No conventional-commit prefix (that's for PRs, not issues).
  • The remaining positional args from $ARGUMENTS (after the type) form the title.
  • Use gh issue create --title "..." --body "$(cat <<'EOF' ... EOF)" --label "...".
  • Labels come from the table above. Do not invent new labels.

Task

  1. Parse $ARGUMENTS:
    • First token: issue type (bug or feature). If missing or invalid, ask the user which template to use.
    • Remaining tokens: title.
  2. Read the matching template file from .github/ISSUE_TEMPLATE/.
  3. Fill every section. Leave no placeholder text. If a section truly has no content, write "N/A" rather than deleting the section.
  4. Auto-inject the branch and last-commit context into "Additional Context".
  5. Run gh issue create with the right labels.
  6. Return the issue URL.

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.