notifications-extract-all

To extract embedded notification text from GitHub Actions workflows into markdown, this Skill uses grep-based detection to find long message bodies in YAML comments, echoes, printf calls, or heredocs, then proposes a diff for human approval before rewriting them into separate Markdown files.

Yes, you can move hard-coded alert messages from shell hook scripts to separate files without changing behavior because the Skill performs byte-for-byte validation of the extracted Markdown content and only rewrites text after explicit human approval.

The safest way to migrate embedded CEO-facing notifications out of workflow files is using a rule-based threshold checking flow that proposes file-by-file diffs, waits for explicit approval, and verifies the migration with strict consistency checks.

Yes, the extraction process avoids modifying secrets and permissions sections in workflow YAML, as the Skill's validation guardrails explicitly preserve exact message content while skipping sensitive configuration sections.

To clean up a noisy GitHub Actions workflow by removing embedded alert text, the Skill scans for eligible notification strings in comments and heredocs, extracts them into a dedicated Markdown file, and preserves runtime behavior through byte-for-byte validation.

A key limitation when extracting notifications from heredocs and printf calls in hook scripts is that the Skill requires explicit human approval for each file-by-file diff proposal before performing any rewrite, ensuring no automated changes occur without review.