plain-text-output
Plain Text Output
This skill ensures that all generated text is strictly plain text, free of any formatting decorations. This is crucial for maintaining compatibility across various systems and ensuring maximum readability in restricted environments like terminals.
Formatting Rules
- No Decoration: Do not use Unicode emojis, bold, or italics (except inside code blocks or when quoting code). Avoiding decorations ensures the text remains completely clean and compatible with systems that do not support rich text.
- Japanese Style: Always use noun-ending (体言止め) by default when writing in Japanese. This creates a concise, objective, and professional tone suitable for documentation and logs.
Examples
Example 1: Documentation Input: We must ensure that the new API endpoints are fully tested before deploying! 🚀 Output: Ensure that the new API endpoints are fully tested before deploying.
Example 2: Japanese Output Input: 新しい機能を追加しました。UIがとても綺麗になりましたね✨ Output: 新機能の追加。UIの改善。
Example 3: Commit Message Input: ✨ feat: added the new login page!! Output: feat: add new login page
More from hrdtbs/agent-skills
plan-self-review
Self-evaluate a plan on a 100-point scale after it is created or updated. Make sure to use this skill immediately whenever you create a plan or update a plan, even if the user does not explicitly ask for a review. This skill ensures that the plan is clear, comprehensive, feasible, and consistent before execution.
45create-pull-request
Create a GitHub pull request safely and reliably using project conventions. Make sure to use this skill whenever the user asks to create a PR, submit changes for review, open a pull request, or mentions "PR", "プルリク", or "pull request". It handles commit verification, branch validation, and PR creation using the gh CLI.
40github-cli
Comprehensive interaction with GitHub repositories, issues, pull requests, and releases using the GitHub CLI (gh). Use this skill whenever the user mentions 'GitHub', 'issues', 'pull requests', 'PRs', 'repositories', 'forks', or needs any interaction with GitHub data, even if they don't explicitly mention 'gh' or 'cli'. This skill MUST be used for all GitHub interactions instead of web scraping or raw API calls.
3bash-best-practices
A comprehensive guide to Bash scripting best practices. Make sure to use this skill whenever the user asks to write, review, refactor, debug, or explain Bash, shell, or sh scripts, even if they don't explicitly mention "best practices". This skill helps write robust, secure, and maintainable shell scripts.
3autonomous-execution
Rules for maximum agent autonomy. Trigger this skill IMMEDAITELY when you feel the need to ask the user a permission question or ask for instructions such as: 'Should I push?', 'Should I run tests?', 'What should I do next?', 'Is this correct?', etc. This skill provides strict guidelines on how to act autonomously, when you are actually allowed to block on the user, and how to verify your own work.
3comprehensive-code-reviewer
A comprehensive, context-aware code review assistant. Use this skill whenever the user asks to review code, look for bugs, check for security vulnerabilities, or improve code quality, even if they just say "review this diff" or "what's wrong with this file?". This skill systematically analyzes code for logic errors, performance bottlenecks, security flaws, and style adherence, providing actionable feedback in a structured format.
3