source-command-celebrate
Celebrate the successful completion of a task to boost team morale.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- source-command-celebrate
- owner
- pm
- scope
- co-abap
- status
- active
- version
- 1.0.0
- metadata
- { "type": "core", "triggers": [ "source-command-celebrate", "celebrate", "task complete" ] }
- description
- Celebrate the successful completion of a task to boost team morale.
- last_reviewed
- 1786752000000
- prerequisites
- none
03 SKILL.md 正文
source-command-celebrate
Use this skill when the user asks to run the migrated source command celebrate (a workspace convention, not a skill).
Command Template
Celebrate
This command is a tool for celebrating when a task has been successfully completed.
Description
Use this to boost team morale after successful code deployment or problem resolution.
Implementation
# Example output pattern
echo "🎉 Task Completed Successfully!"
echo "🚀 ABAP Objects Deployed and Activated."
echo "✨ Great job, Team!"
Context
A simple morale-boosting skill triggered when a task or deployment completes successfully. It provides a standardized celebration message to acknowledge team effort and maintain positive momentum throughout the development workflow.
When to Use
- After successfully completing a development task or sprint
- After a successful code deployment or transport release
- When the user explicitly requests a celebration or morale boost
- After resolving a difficult bug or problem
Execution Steps
- Confirm the task or deployment has completed successfully.
- Output a celebratory message acknowledging the achievement.
- Optionally reference specific metrics (objects deployed, tests passed, etc.).
Output Format
A brief, encouraging message confirming task completion. Example:
Task Completed Successfully!
ABAP Objects Deployed and Activated.
Great job, Team!
Related Skills
- abap-dev — Core ABAP development workflows whose completion may trigger celebration
- post-write-chain — QA chain that must pass before celebrating a successful deployment
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.