Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

feat: a skill that finds where the session's skills didn't fit and files the gaps

Đang mở
  • Có gì không ổn?
#6,417 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
22/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
shell
Lĩnh vực
ai, developer-experience, tooling

Hướng nghiên cứu

This is a new skill (suggested names /plugin-quality:fit-gaps or /session-flow:skill-fit) that must read on-disk session transcripts and subagent returns, attribute gaps to owning plugins, de-duplicate with gh issue list --search, and only file issues after owner confirmation. Start from the existing skills named in the issue (/discipline:use-your-skills, /plugin-quality:audit, /session-flow:retro) and from session dba79e68-af19-4ecc-a0ce-69d8b1dbefbb plus issues #6412 and #6413 as the intended output. Done means the skill presents a ledger and files evidence-first issues only on yes; this is product design, not a one-file edit.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

needs-human needs-triage

Problem

When a skill doesn't fit the work in front of it, the session quietly works around it. That workaround is the most useful feedback a plugin can get, and today it is lost unless someone notices and files it by hand.

In the 2026-10-04 CI-performance session the owner asked for that by hand twice. Each time the coordinator reconstructed the gaps from memory and filed #6412 and #6413. The gaps it found:

  • implement-dispatch needs a PLAN.md, but the work came as scoped audit output, so workers were hand-dispatched with re-typed lifecycle rules;
  • workers stalled five times waiting on their own background work;
  • a research skill's verifier failed twice on labeling for vendor-documented facts, so the loop was stopped by judgment;
  • workers' classifier denials could not see the owner's approval, so edits were escalated to the main session.

Existing skills cover parts but not this:

  • /discipline:use-your-skills finds a skill that should have fired, not one that fired and didn't fit.
  • /plugin-quality:audit audits one named component after use, not a whole session's fit.
  • /session-flow:retro codifies session learnings, not per-skill gaps routed to their owners.

Ask

A skill the owner can fire at any point (start, middle or end), for example /plugin-quality:fit-gaps or /session-flow:skill-fit. It would:

  1. Read the session's on-disk transcript and its subagents' returns. Find each place where:
    • a skill was invoked and then bypassed or overridden;
    • a coordinator re-typed the same rules into several briefs;
    • a worker stalled, or was nudged or re-briefed for the same reason more than once;
    • a permission or classifier denial forced a workaround;
    • a verifier loop was stopped by judgment;
    • the owner asked "is there a skill for this".
      At session start, with no transcript yet, it instead lists the skills that likely apply to the stated task and their known fit limits, from open issues.
  2. Attribute each gap to its owning plugin or skill, citing transcript evidence.
  3. De-duplicate against that plugin's open issues (gh issue list --search).
  4. Present a ledger of gap, owning skill, evidence, proposed change and existing issue. File the new ones only on the owner's yes, with evidence-first bodies. That fits the org's rule that no automated process opens issues.
  5. Optionally propose a new-skill candidate when no existing skill owns a recurring pattern.

Evidence

Session dba79e68-af19-4ecc-a0ce-69d8b1dbefbb, plus #6412 and #6413, which this skill would have produced.

Ngôn ngữ chính
Shell
Star
22
Fork
2
Merge trung bình
5 giờ 11 phút
Pull request đã merge (30 ngày)
838

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của melodic-software/claude-code-plugins

Tất cả issue của melodic-software/claude-code-plugins

Issue tương tự

Thêm issue về Shell/Bash

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.