agentleFS
Sign inStart free
mavrovdemavrovde/thekotlin.com/.claude/skills/issue-workflow/SKILL.md

issue-workflow

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Issue-driven development for TheKotlin.com — the 8-section issue template, the milestone/label taxonomy (including forum-specific areas like ai-agents and content), and the close-the-loop rule. Load when creating or triaging issues, wiring Closes #NN into a PR, or closing out landed work.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. Cosmian/kms★ 372same name
    2. LuisUrrutia/skills★ 2same name
    3. Chrike/coding-agent-skills★ 1same name
    4. ragna-ai/ragna-studio★ 1same name
    5. TruthHun/issue-workflow★ 0same name

    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.

  • In this repository4 other files it gives its agents.

The file

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 5 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. Distinctive:

    Every issue has: a milestone + exactly one priority label + ≥1 area label + a type label.

    line 16
  2. Very specific:

    Verify names exist before use (gh label list, gh api .../milestones --jq '.[].title').

    line 24
  3. Very specific:

    After merge: comment on the issue with the PR link, merge SHA, the CI & Deployment run result, and each acceptance criterion with who …

    line 38

“Common” is measured: kept by at least 6 in 10 of the 5 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 workflow — TheKotlin.com

Issues are the project notebook: every idea, bug, content plan, agent-charter change, and research decision lives as an issue — not in chat or private memory.

Invariant — no orphan issues

Every issue has: a milestone + exactly one priority label + ≥1 area label + a type label.

  • Milestones: Forum core · Human–AI communication · Content & knowledge base · SEO & growth · Security & hardening · Reliability & bug fixes · CI/CD, tooling & docs
  • Priority: P0-critical P1-high P2-medium P3-low
  • Area: backend frontend admin infra ci-cd forum content ai-agents seo security
  • Type: bug enhancement documentation dependencies security

Verify names exist before use (gh label list, gh api .../milestones --jq '.[].title'); bootstrap missing ones (gh label create, gh api -X POST .../milestones) rather than inventing per-issue variants.

Template (all 8 sections, in order)

Summary · Why it matters (tie to the north star) · Impact · Current state (grounded, path:line you actually read) · Proposed action (numbered) · Acceptance criteria (- [ ], objectively checkable) · How to verify (commands + expected output) · Links.

PRs

Closes #NN/Refs #NN for every addressed issue; the body maps each acceptance criterion to how the diff satisfies it. Type + area labels on the PR mirror the issue's.

Close-the-loop (mandatory)

After merge: comment on the issue with the PR link, merge SHA, the CI & Deployment run result, and each acceptance criterion with who verified it and what they ran. A bare auto-close leaves no record — the comment IS the record.

Safety

Public-facing project: no secrets, JWT values, or working exploits in issues — config locations and vulnerability classes only.

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.

Check your setup, free