krammechangelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of ma...
发现 devops project management 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of ma...
Display information about the current project or a specified path
Display routing correlation statistics - how well the skill router predicts actual skill usage
Audit de conformité d'une database Notion entière. Calcule le % de pages conformes, identifie les pages orphelines. Use when auditing databases or planning template migrations.
Index of available skills with triggers. Use FIRST when starting any task to check which skill might help.
Local-first GitHub issue planning and synchronization system. Use this skill when planning projects locally, creating issue files in .issues/, working with the /plan-issue, /update-issue, /sync-issue, /list-iss...
Compact marimo notebook patterns. Reactive cells, UI elements, data visualization.
Update the chronological events index with deep understanding of transcripts, messages, and communications. Use when user says "update timeline", "index events", or "process transcripts".
Updates Linear issues based on project-status evidence. Use when asked to sync Linear with code evidence or update issue status.
Verify implementation status by querying Linear API for issues. Use when checking issue tracking status.
Reports implementation status of project components with evidence. Use when asked about what's done, in progress, or planned for a project.
Write Product Requirements Documents (PRDs) with structured workflow. Triggers: 'write a PRD', 'product spec', 'feature requirements', 'product requirements', 'create PRD', or any request to document product/fe...
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design plann...
Use before design phase to challenge assumptions and surface risks
Use when you have a written implementation plan to execute
Use when reviewing design documents, technical specifications, or architecture docs before implementation planning
Use when reviewing implementation plans before execution, especially plans derived from design documents
Interactive command-line tool for Atlassian Jira. This skill should be used when users want to interact with Jira issues, epics, sprints, or when they mention Jira workflows, issue management, or need help with...
Fast decision-making methodology for time-critical situations. Use when you have minutes (not hours) to decide, during incidents, emergencies, or hard deadlines. Optimizes for "good enough now" over "perfect la...
Advanced recursive reasoning methodology for systematic problem-solving. Use when you need to explore multiple solution approaches in parallel, evaluate them rigorously, and recursively deepen the best path. Id...
Sequential reasoning with deep self-reflection and backtracking. Use when problems have step-by-step dependencies, need careful logical reasoning, or require error correction. Each step includes self-reflection...
Red-team thinking for robustness testing and edge case discovery. Use when you need to stress-test solutions, find vulnerabilities, anticipate failures, or challenge assumptions. Ideal for security review, syst...
Provides standardized Git workflows, commit message conventions, branching strategies, and collaboration patterns for all agents performing Git operations. Use when creating commits, choosing branching strategi...
This skill should be used when the user asks to "analyze fix commits and generate postmortems", "create postmortems from git history", or "summarize bug fixes into postmortem reports".
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。