@callumvass/forgeflow-dev 0.4.4 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -103,6 +103,10 @@ PRBODY
103
103
  gh pr create --title "My title" --body-file /tmp/pr-body.md
104
104
  ```
105
105
 
106
+ ## Commit Style
107
+
108
+ Use [Conventional Commits](https://www.conventionalcommits.org/). Read `git log --oneline -10` before your first commit to match the repo's existing style. Common prefixes: `feat:`, `fix:`, `test:`, `refactor:`, `chore:`, `docs:`. Keep messages concise (under 72 chars).
109
+
106
110
  ## Before Committing
107
111
 
108
112
  - **Reachability check**: Every new module, class, or function you created must be imported and called from production code — not just from tests. Trace from the entry point to your new code.
@@ -37,3 +37,4 @@ You are a refactorer agent. You run after a feature has been implemented to find
37
37
  - **Keep it small**: Each refactoring should be a single, focused change.
38
38
  - **If nothing to do, say so**: "No refactoring needed" is a perfectly valid outcome.
39
39
  - **Preserve public interfaces**: Don't rename or restructure exports without updating all callers.
40
+ - **Commit style**: Use [Conventional Commits](https://www.conventionalcommits.org/). Read `git log --oneline -10` before committing to match the repo's style. Use `refactor:` prefix.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@callumvass/forgeflow-dev",
3
- "version": "0.4.4",
3
+ "version": "0.5.0",
4
4
  "type": "module",
5
5
  "description": "Dev pipeline for Pi — TDD implementation, code review, architecture, and skill discovery.",
6
6
  "keywords": [