agentleFS
IjonTychyIjonTychy/brain-ios/.claude/skills/bug-triage/SKILL.md

bug-triage

Skill1 starsChanged 8 months agoUnlicenseView on GitHub

Bug-Triage fuer brain-ios. Kategorisiert, priorisiert und dokumentiert Bugs in BUG-REPORT.md. Nutze diesen Skill um neue Bugs einzutragen oder den Bug-Report zu aktualisieren.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ao-desktop-dev and pr-description.

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.
  • agentlab-inSkill

    ao-desktop-dev

    Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.

    Also in 5 projects that use this

  • MicrosoftSkill

    pr-description

    Draft Nacelle PR titles, pull request descriptions, commit titles, commit descriptions, and squash commit messages. Use when asked for PR or commit wording, a branch summary, or a PR description that can be used in a commit. Omit validation sections from commit bodies and remove filler.

    Also in 4 projects that use this

The file

Files
SKILL.md

Bug-Triage — brain-ios

Verwaltet den Bug-Report fuer das brain-ios Projekt.

Kommandos

Neuer Bug ($ARGUMENTS beginnt mit "new")

  1. Lies BUG-REPORT.md
  2. Bestimme die naechste Bug-ID (BUG-NNN)
  3. Kategorisiere den Bug:
    • Runtime: Skill-Engine, Render, Action, Logic
    • UI: SwiftUI Views, Navigation, Layout
    • Data: GRDB, Migrations, Queries
    • LLM: Provider, Router, Streaming
    • Bridge: iOS Bridges (Contacts, EventKit, etc.)
    • Build: Xcode Cloud, pbxproj, SPM
    • Security: Keychain, Auth, Pinning
  4. Priorisiere:
    • P0 Critical: App crasht, Datenverlust
    • P1 High: Feature kaputt, Security-Issue
    • P2 Medium: Falsche Darstellung, UX-Problem
    • P3 Low: Kosmetisch, Nice-to-have
  5. Trage den Bug in BUG-REPORT.md ein

Update ($ARGUMENTS = "update")

  1. Lies BUG-REPORT.md
  2. Pruefe via git log und Code-Analyse ob Bugs behoben wurden
  3. Aktualisiere Status (OFFEN → BEHOBEN) mit Commit-Referenz

Statistik ($ARGUMENTS = "stats")

  1. Lies BUG-REPORT.md
  2. Zaehle nach Kategorie und Prioritaet
  3. Zeige Zusammenfassung

Bug schliessen ($ARGUMENTS beginnt mit "close")

  1. Finde den Bug anhand der ID
  2. Markiere als BEHOBEN mit Datum und Begruendung

Bug-Format in BUG-REPORT.md

### BUG-NNN: [Kurzbeschreibung]
- **Kategorie:** Runtime/UI/Data/LLM/Bridge/Build/Security
- **Prioritaet:** P0/P1/P2/P3
- **Status:** OFFEN / BEHOBEN / WONTFIX
- **Datei:** [betroffene Datei(en)]
- **Beschreibung:** [Details]
- **Behoben:** [Datum, Commit] (nur wenn behoben)

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.