project-workflow
Provides workflow guidelines for problem-solving, git commits, GitHub issues, PRs, build management, and testing. Use when planning tasks, creating issues, submitting PRs, managing builds, or writing tests.
When & Why to Use This Skill
The Project Workflow skill is a comprehensive framework designed to standardize the software development lifecycle. It provides structured guidelines for systematic problem-solving, Git version control, and GitHub management. By enforcing best practices like the 5W1H framework for issues/PRs and conventional commit formats, it ensures project consistency, high-quality documentation, and efficient team collaboration.
Use Cases
- Standardizing Version Control: Implementing conventional commit formats to maintain a clean, readable, and professional Git history.
- Optimizing GitHub Collaboration: Using the 5W1H framework (Who, What, Where, When, Why, How) to create detailed, actionable issues and pull requests that reduce communication overhead.
- Establishing Testing Protocols: Setting up a layered testing infrastructure, including unit, integration, and E2E tests, to ensure software reliability and prevent regressions.
- Structured Task Planning: Following systematic procedures for organizing development tasks, managing builds, and handling performance analysis efficiently.
| name | project-workflow |
|---|---|
| description | Provides workflow guidelines for problem-solving, git commits, GitHub issues, PRs, build management, and testing. Use when planning tasks, creating issues, submitting PRs, managing builds, or writing tests. |
Project Workflow Skill
When to Use
- Planning and organizing tasks
- Creating GitHub issues or PRs
- Writing commit messages
- Managing builds and dependencies
- Setting up testing infrastructure
Reference Documents (Import Syntax)
Workflow
@reference/workflow.md @reference/question-handling.md @reference/workflow-problem-solving.md @reference/performance-analysis.md
GitHub
@reference/github-issue-5w1h.md @reference/github-pr-5w1h.md @reference/git-commit-format.md
Project Management
@reference/problem-solving.md @reference/build.md @reference/testing.md
Core Principles
- Systematic approach: Follow procedures step by step
- Minimal changes: Modify existing files, create new ones only when necessary
- Conventional commits: Use proper type(scope): description format
- 5W1H framework: Apply What, Why, Who, When, Where, How for issues and PRs
- Layered testing: Unit tests (many) -> Integration tests (some) -> E2E tests (few)