Writing & Content
PromptBeginner5 minmarkdown
- Content is organized by priority (safety first
then workflow)
0
Explore
Find agent skills by outcome
14,124 skills indexed with the new KISS metadata standard.
Showing 24 of 14,124Categories: Data & Insights, Communication, Coding & Debugging, Data, Creative, Writing & Content
Writing & Content
PromptBeginner5 minmarkdown
- No content duplicates README
style guides
0
Data
PromptBeginner5 minmarkdown
- Database migration safety (ordering
rollback
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Critical repo-specific safety rules (migration ordering
API contract stability)
0
Writing & Content
PromptBeginner5 minmarkdown
- Organize content into tight
skimmable sections with bullet points
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Remove generic best practices (e.g.
write clean code
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Identify safety-critical constraints (migrations
API contracts
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Discover non-obvious workflow constraints (e.g.
codegen order
0
Creative
PromptBeginner5 minmarkdown
You are a senior repository workflow expert and specialist in coding agent instruction design
AGENTS.md authoring
0
Writing & Content
PromptBeginner5 minmarkdown
Repository Workflow Editor Agent Role
# Repo Workflow Editor
0
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_git-workflow-expert.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,...
0
Coding & Debugging
PromptBeginner5 minmarkdown
Write all proposed workflow changes and any code snippets to `TODO_git-workflow-expert.md` only. Do not create any other files. If specific files should be created or edited
include patch-style diffs or clearly labeled file blocks inside the TODO.
0
Writing & Content
PromptBeginner5 minmarkdown
- **Vague commit messages** (fix stuff
updates): Destroys the usefulness of git history
0
Writing & Content
PromptBeginner5 minmarkdown
- **Force-pushing to shared branches**: Rewrites history for all collaborators
causing lost work and confusion
0
Writing & Content
PromptBeginner5 minmarkdown
- Never rewrite history on shared branches (main
develop
0
Creative
PromptBeginner5 minmarkdown
- Never commit generated files
build artifacts
0
Writing & Content
PromptBeginner5 minmarkdown
- Write conventional commit messages (`feat:`
`fix:`
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Use merge tools (VS Code
IntelliJ
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Implement git hooks** for automated code quality checks
commit message validation
0
Creative
PromptBeginner5 minmarkdown
- **Design branching strategies** recommending appropriate models (Git Flow
GitHub Flow
0
Writing & Content
PromptBeginner5 minmarkdown
- **Manage commit history** through interactive rebasing
squashing
0
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_env-config.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandemi...
0
Coding & Debugging
PromptBeginner5 minmarkdown
Write all proposed configurations and any code snippets to `TODO_env-config.md` only. Do not create any other files. If specific files should be created or edited
include patch-style diffs or clearly labeled file blocks inside the TODO.
0
Coding & Debugging
PromptBeginner5 minmarkdown
### Python (python-dotenv
pydantic-settings)
0