Apply Explore, Plan, Code, and Commit workflow to software changes.
npx skills add https://github.com/BinkyTwin/DeepRead --skill epcp-workflow
Please help me install this Agent Skill. Skill: epcp-workflow Source: https://github.com/BinkyTwin/DeepRead/tree/main/.claude/skills/epcp-workflow Command: npx skills add https://github.com/BinkyTwin/DeepRead --skill epcp-workflow
This Skill enforces a disciplined Explore → Plan → Code → Commit workflow to prevent hasty, unverified coding. It increases reliability and traceability by requiring exploration, planning, incremental coding, and clean commits.
Start by exploring the repository to gather context, then generate a plan with acceptance criteria, proceed to code in small steps, run verification, and finish with a clean commit message.
High-intent search queries and answers about installing and using this skill.
A reliable git workflow enforces exploration, planning, coding, and committing in sequence. Read key files first, create a concrete plan with acceptance criteria, implement incrementally with verification, then commit with a clear message. This prevents hasty changes and maintains clean history.
Planning before code identifies risks, edge cases, and concrete steps upfront, reducing rework and unverified changes. A plan with acceptance criteria ensures you know what success looks like before implementation and helps catch problems early.
Commit incrementally after each verified step with a conventional message that describes what changed and why. Clean commits make the history readable, enable easy rollbacks, and support optional pull requests for review.
Apply the Explore → Plan → Code → Commit workflow to both feature work and bug fixes. Explore to gather context, plan with concrete steps, code and verify incrementally, then commit with clear history. Subagents can parallelize exploration for faster planning.
Yes. The Explore → Plan → Code → Commit workflow applies to feature work, bug fixes, refactors, and integrations. The same disciplined approach—reading files first, planning steps, incremental coding with verification—prevents unreliable changes across all task types.
Pull requests are optional. The workflow enforces clean commits with clear messages. Optionally open a PR afterward for team review, but the core discipline—exploration, planning, verification, and committed history—works standalone or with PR creation.
u9401066Initialize a new project from a template with Git reset and configuration.
tachiiri-orgCreate a pull request from the dev branch to main after verifying branch and remote state.
mcj-coderConfigure Git branching strategies, Conventional Commits, and merge rules.
SoloXLabBreak unstructured software requirements into executable steps with validation checkpoints.
