CommunitySchreiben & Editierengithub.com

Arzaroth/skills

Fill a ticket's technical post-mortem - write the whole root cause + fix into one tracker field (no restating the initial symptom), then point the other analysis fields at it ("see dev notes"). Tracker, fields, language and headings come from the config. Invoke for a given ticket or the fix in progress. Triggers - "analyse des causes", "analyse technique", "root cause", "cause racine", "solution apportée", "/analyse-causes".

Was ist skills?

skills is a Claude Code agent skill that fill a ticket's technical post-mortem - write the whole root cause + fix into one tracker field (no restating the initial symptom), then point the other analysis fields at it ("see dev notes"). Tracker, fields, language and headings come from the config. Invoke for a given ticket or the fix in progress. Triggers - "analyse des causes", "analyse technique", "root cause", "cause racine", "solution apportée", "/analyse-causes".

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Arzaroth/skills/tree/HEAD/skills/analyse-causes

Installed? Explore more Schreiben & Editieren skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Ticket technical post-mortem (one field + pointers)

The user puts everything in one field and points the other analysis fields to it, so nothing is said twice. Reproduce that workflow.

Config

Read ~/.config/skills/analyse-causes/config.md before anything else. It sets the tracker and its tools, the project and ticket key pattern, the field format, the write-up language and headings, the write-up field, the deflected fields with their pointer text, and the MR link fields. If it is missing, tell the user to copy config.example.md (next to this file) to ~/.config/skills/analyse-causes/config.md and fill it in, and stop.

Target: the ticket passed as argument, otherwise the fix in progress in the session (diff / branch / MR).

What to produce

One complete write-up, in the configured language, in markdown, with two sections under the configured headings:

  1. Root cause - the technical WHY. Do NOT restate the initial situation (symptom / ticket description). Go back to the real origin: design choice, constant / file:line, wrong assumption. Never the visible symptom.
  2. Fix - what changed and why it removes the root cause. Factual: chosen mechanism, files/constants touched, resulting behaviour. No MR link here: it goes in the configured MR link fields.

Rules: concise, short bullets, exact terms (constants, functions, file:line), checked against the real code. No em-dash (U+2014) - hyphen, comma, or rephrase.

Procedure

  1. Identify the ticket: argument = key matching the configured pattern; otherwise the fix in progress (diff / branch / MR of the session).
  2. Read the ticket through the configured tool if needed, but do not copy its description.
  3. Trace the root cause in the code and list the fix's changes (git diff / MR).
  4. Write the complete write-up.
  5. Show it, then write the fields in the configured format:
    • write-up field <- the complete write-up
    • each deflected field <- a one-paragraph document with the configured pointer text If no ticket is targeted (a fix in session without a key), only show the write-up and offer to fill the fields.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

Arzaroth/skills

Work one round of review comments on a pull/merge request: fetch every unresolved thread, verify each finding against the current code, fix what is still valid, reply with a justification to what is not, then commit, push and answer every thread. Use when a PR has review comments to deal with - from an AI reviewer (CodeRabbit and friends) or a human - and when asked to 'address the review', 'fix the review comments', 'respond to CodeRabbit', or 'handle the PR feedback'. The babysit-pr skill calls this for each of its rounds.

Arzaroth/skills

Open a pull/merge request and stay with it until it merges: trigger the reviewers, watch for their verdict, work each round of findings, push, re-trigger, and merge when it is clean. Handles AI reviewers (CodeRabbit) and human maintainers, on GitHub (gh) and GitLab (glab). Use when asked to 'open a PR and babysit it', 'ship this and see it through', 'get this PR merged', 'watch the PR until it lands', or '/babysit-pr'. Also the review-and-merge half of ship-feature-pipeline.

Arzaroth/skills

Check whether the repo's own docs still describe the code after recent changes, and update the ones that went stale. Scopes itself to the last merged branch, the last commit, this session's work, or a full sweep. Use when asked to 'update the docs', 'check the docs', 'are the docs still accurate', 'docs sweep', 'refresh the documentation', or '/docs-update'. Every line it writes goes through the unslop skill. Run it before cutting a release or merging a feature, so docs ship with the change instead of trailing it.

Arzaroth/skills

Cut a release on GitHub: update the changelog, bump the version (preferring the repo's own release task or script over a manual edit), tag, push, then watch the release workflow until the GitHub Release exists. Use when asked to 'cut a release', 'release version X', 'ship a new version', 'bump the version and tag', 'publish a release', or '/gh-release'. For repos where a tag push triggers a GitHub Actions workflow that creates the release.

Verwandte Skills