القائمة
Compose a structured feedback report for a harness artifact problem — gathers required context and formats it clearly for submission as a GitHub issue, PR description, or message.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.
Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.
Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."
Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.
End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.
Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.
| name | compose-feedback |
| description | Compose a structured feedback report for a harness artifact problem — gathers required context and formats it clearly for submission as a GitHub issue, PR description, or message. |
Use this skill to build a well-structured feedback report before submitting. A good report has enough context for the maintainer to reproduce and understand the problem without follow-up questions.
Required fields for a complete report:
Optional but useful:
Issue title format:
[artifact-type] Brief description of the problem
Example: [hooks-artifact] PreToolUse hook not firing in Cursor plugin format
PR description format (for fix submissions):
Gather missing fields by asking the user one question at a time before composing the final report. Do not submit with unknown or vague fields — a weak report is worse than no report.
