ai-workflow-init 1.2.1 → 1.2.2
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.
|
@@ -54,7 +54,13 @@ If creating implementation doc for first task:
|
|
|
54
54
|
- `## Follow-ups` - TODOs or deferred work
|
|
55
55
|
- Follow the template format strictly
|
|
56
56
|
|
|
57
|
-
## Step 5:
|
|
57
|
+
## Step 5: Quality Checks
|
|
58
|
+
After completing Step 4 for each task batch:
|
|
59
|
+
- Run linting on changed files (e.g., `eslint` if JavaScript/TypeScript project).
|
|
60
|
+
- Run type checks if applicable (e.g., `tsc --noEmit`).
|
|
61
|
+
- Fix issues (up to 3 attempts) before proceeding to the next task.
|
|
62
|
+
|
|
63
|
+
## Step 6: Next Actions
|
|
58
64
|
After completing tasks:
|
|
59
65
|
- Suggest running `code-review` to verify against standards
|
|
60
66
|
- Suggest running `writing-test` if edge cases need coverage
|
|
@@ -9,13 +9,15 @@ Initialize a new chat by loading and aligning to `AGENTS.md` so the AI agent con
|
|
|
9
9
|
|
|
10
10
|
## Steps
|
|
11
11
|
1) Open and read `AGENTS.md` (project root).
|
|
12
|
-
2)
|
|
12
|
+
2) Detect project languages/frameworks/libraries from repository metadata (e.g., `package.json`, `pyproject.toml`, lockfiles, config files). Update `docs/ai/project/CODE_CONVENTIONS.md` to include any missing key coding conventions (only important items like React, TypeScript, TailwindCSS, etc.).
|
|
13
|
+
3) Read files in `docs/ai/project/` to understand project context and standards.
|
|
14
|
+
4) Produce a short confirmation in the chat including:
|
|
13
15
|
- Workflow alignment: Plan → Implement → Test → Review
|
|
14
16
|
- Tooling strategy: semantic search first; parallelize independent steps
|
|
15
17
|
- Communication: minimal Markdown; status updates; high-signal summaries; mirror user language (default English if unclear)
|
|
16
18
|
- Code presentation: code references for existing code; fenced blocks for new code
|
|
17
19
|
- TODO policy: create/update todos; keep only one `in_progress`
|
|
18
|
-
|
|
20
|
+
5) If any section is missing or unclear, ask a single concise clarification question; otherwise proceed silently in future commands.
|
|
19
21
|
|
|
20
22
|
## Output format (concise)
|
|
21
23
|
- Use the language of the triggering user message (mirror). If ambiguous, use English.
|