@ahumandev/autocode 0.0.1 → 0.0.3

package/README.md

@@ -1,6 +1,6 @@
-<p align="center"><img src="docs/logo.webp" alt="AutoCode"/></p>
+***The workflow engine for traceable autonomous job execution***
 
-<h3 align="center">The workflow engine for traceable autonomous job execution</h3>
+<p align="center"><img src="docs/logo.webp" alt="AutoCode"/></p>
 
 ---
 
@@ -185,7 +185,7 @@ Normal prompts can start or resume work. Slash commands are convenience wrappers
 | `/repeat-as-md`   | Repeats the last response inside a fenced Markdown code block.                       |
 | `/repeat-as-wiki` | Repeats the last response in Atlassian Wiki Markup for Jira-style pasting.           |
 | `/report-session` | Reports on the entire current session.                                               |
-| `/report-task`    | Reports on only the most recent user-requested assignment.                           |
+| `/report-last`    | Reports on only the most recent user-requested assignment.                           |
 | `/resume`         | Resumes an interrupted session by calling the resume tool.                           |
 
 ### Job files

package/dist/agents/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/agents/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAA;AACtD,OAAO,KAAK,EAAE,sBAAsB,EAAE,SAAS,EAAE,gBAAgB,EAAE,MAAM,UAAU,CAAA;AACnF,OAAO,EAA8B,KAAK,6BAA6B,EAAE,MAAM,iBAAiB,CAAA;AA0ChG,KAAK,qBAAqB,GAAG,MAAM,CAAC,MAAM,EAAE,gBAAgB,CAAC,CAAA;AAC7D,KAAK,sBAAsB,GAAG,gBAAgB,GAAG,qBAAqB,CAAA;AACtE,KAAK,2BAA2B,GAAG,MAAM,CAAC,MAAM,EAAE,sBAAsB,CAAC,CAAA;AACzE,KAAK,wBAAwB,GAAG;IAC5B,IAAI,CAAC,EAAE,gBAAgB,GAAG,2BAA2B,CAAA;IACrD,CAAC,GAAG,EAAE,MAAM,GAAG,sBAAsB,GAAG,2BAA2B,GAAG,SAAS,CAAA;CAClF,CAAA;AACD,MAAM,MAAM,mBAAmB,GAAG,IAAI,CAAC,WAAW,EAAE,YAAY,CAAC,GAAG;IAAE,UAAU,CAAC,EAAE,gBAAgB,GAAG,wBAAwB,CAAC;IAAC,IAAI,CAAC,EAAE,SAAS,CAAA;CAAE,CAAA;AAClJ,KAAK,mBAAmB,GAAG,mBAAmB,CAAA;AAC9C,KAAK,QAAQ,GAAG,MAAM,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAAA;AAEnD,KAAK,4BAA4B,GAAG,MAAM,CAAC,QAAQ,GAAG,6BAA6B,CAAA;AAsFnF,wBAAgB,4BAA4B,CACxC,MAAM,EAAE,QAAQ,EAChB,mBAAmB,GAAE,sBAA2B,GACjD,QAAQ,CA6BV;AAED,wBAAgB,0BAA0B,CAAC,MAAM,EAAE,QAAQ,EAAE,OAAO,GAAE,4BAAiC,GAAG,QAAQ,CAoBjH;AAglCD,wBAAgB,WAAW,CACvB,mBAAmB,GAAE,sBAA2B,EAChD,sBAAsB,CAAC,EAAE,6BAA6B,GACvD,QAAQ,CAEV;AAED,wBAAgB,kBAAkB,CAAC,SAAS,EAAE,MAAM,EAAE,mBAAmB,GAAE,sBAA2B,GAAG,mBAAmB,CAAC,YAAY,CAAC,CAEzI;AAED,wBAAgB,YAAY,CAAC,SAAS,EAAE,MAAM,GAAG,SAAS,GAAG,SAAS,CAErE;AAED,eAAO,MAAM,MAAM,EAAE,QAAwB,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/agents/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAA;AACtD,OAAO,KAAK,EAAE,sBAAsB,EAAE,SAAS,EAAE,gBAAgB,EAAE,MAAM,UAAU,CAAA;AACnF,OAAO,EAA8B,KAAK,6BAA6B,EAAE,MAAM,iBAAiB,CAAA;AA0ChG,KAAK,qBAAqB,GAAG,MAAM,CAAC,MAAM,EAAE,gBAAgB,CAAC,CAAA;AAC7D,KAAK,sBAAsB,GAAG,gBAAgB,GAAG,qBAAqB,CAAA;AACtE,KAAK,2BAA2B,GAAG,MAAM,CAAC,MAAM,EAAE,sBAAsB,CAAC,CAAA;AACzE,KAAK,wBAAwB,GAAG;IAC5B,IAAI,CAAC,EAAE,gBAAgB,GAAG,2BAA2B,CAAA;IACrD,CAAC,GAAG,EAAE,MAAM,GAAG,sBAAsB,GAAG,2BAA2B,GAAG,SAAS,CAAA;CAClF,CAAA;AACD,MAAM,MAAM,mBAAmB,GAAG,IAAI,CAAC,WAAW,EAAE,YAAY,CAAC,GAAG;IAAE,UAAU,CAAC,EAAE,gBAAgB,GAAG,wBAAwB,CAAC;IAAC,IAAI,CAAC,EAAE,SAAS,CAAA;CAAE,CAAA;AAClJ,KAAK,mBAAmB,GAAG,mBAAmB,CAAA;AAC9C,KAAK,QAAQ,GAAG,MAAM,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAAA;AAEnD,KAAK,4BAA4B,GAAG,MAAM,CAAC,QAAQ,GAAG,6BAA6B,CAAA;AAsFnF,wBAAgB,4BAA4B,CACxC,MAAM,EAAE,QAAQ,EAChB,mBAAmB,GAAE,sBAA2B,GACjD,QAAQ,CA6BV;AAED,wBAAgB,0BAA0B,CAAC,MAAM,EAAE,QAAQ,EAAE,OAAO,GAAE,4BAAiC,GAAG,QAAQ,CAoBjH;AA4lCD,wBAAgB,WAAW,CACvB,mBAAmB,GAAE,sBAA2B,EAChD,sBAAsB,CAAC,EAAE,6BAA6B,GACvD,QAAQ,CAEV;AAED,wBAAgB,kBAAkB,CAAC,SAAS,EAAE,MAAM,EAAE,mBAAmB,GAAE,sBAA2B,GAAG,mBAAmB,CAAC,YAAY,CAAC,CAEzI;AAED,wBAAgB,YAAY,CAAC,SAAS,EAAE,MAAM,GAAG,SAAS,GAAG,SAAS,CAErE;AAED,eAAO,MAAM,MAAM,EAAE,QAAwB,CAAA"}

package/dist/agents/prompts/execute_git_commit.d.ts

@@ -1,2 +1,2 @@
-export declare const executeGitCommitPrompt = "\n# Git Commit Agent\n\nYour role is to review recent changes and create a professional git commit with a well-structured message.\n\n---\n\n## Workflow\n\n1. Review Changes\n2. Add Unstaged Files\n3. Generate Commit Message\n4. Commit Changes\n\n### STEP 1: Review Changes\n\n1. Summarize user request to \"git commit purpose\" in < 50 characters\n2. If \"git commit purpose\" is not clear, task `query_git` subagent to get diff of staged and unstaged changes and analyze the diff and determine \"git commit purpose\"\n\n### STEP 2: Add Unstaged Files\n\nUnless already committed or if user specifically requested it, NEVER commit:\n- .env files or any files with passwords\n- .idea/\n- .vscode/\n- .DS_Store\n- node_modules\n- Thumbs.db\n- Temporary test, script or md files generated by AI models for debugging/reporting purposes\n\nSpecifically add files that:\n- match \"git commit purpose\"\n- AGENTS.md, README.md (if they exist)\n\nFor every unstaged file:\n\nDecide if it should be included in commit:\n   - If yes, task `git_git_add` to stage it\n   - If no, ignore it\n\n### STEP 3: Generate Commit Message\n\nCommit Caveman English message in format:\n\n```\n[ticket id] [type]([scope]) - [description]\n\n[motivation]\n\n[difference]\n\n[breaking changes]\n```\n\nReplace [placeholders] with:\n\n- [ticket id] to be replaced by ticket id if known:\n   - Is optional\n   - Format: [PROJECT]-[NUMBER]:\n   - Examples: CARDATA-1234, MYPROJECT-10000\n- [type] to be replaced by:\n   - `feat` Commits that add, adjust or remove a new feature to the API or UI\n   - `fix` Commits that fix an API or UI bug of a preceded `feat` commit\n   - `refactor` Commits that rewrite or restructure code without altering API or UI behavior\n   - `perf` Commits are special type of `refactor` commits that specifically improve performance\n   - `style` Commits that address code style (e.g., white-space, formatting, missing semi-colons) and do not affect application behavior\n   - `test` Commits that add missing tests or correct existing ones\n   - `docs` Commits that exclusively affect documentation\n   - `build` Commits that affect build-related components such as build tools, dependencies, project version, ...\n   - `ops` Commits that affect operational aspects like infrastructure (IaC), deployment scripts, CI/CD pipelines, backups, monitoring, or recovery procedures, ...\n   - `chore` Commits that represent tasks like initial commit, modifying `.gitignore`, ...\n- [scope] to provides additional contextual information:\n   - Is optional, omit if scope is unknown\n   - Allowed scopes vary and are typically defined by the specific project\n   - NEVER use issue identifiers as scopes\n- [breaking changes] to be replaced by:\n   - Only include section if commit introduces breaking changes\n   - Commit with breaking changes MUST be indicated by an `!` before the `: ` in the subject line e.g. `feat(api)!: remove status endpoint`\n   - Breaking changes **should** be described in the [commit footer section](#footer), if the [commit description](#description) isn't sufficiently informative\n- [description] to be replaced by concise description of the change. \n   - Is a **mandatory** part\n   - Description is < 50 characters\n   - **NEVER** capitalize the first letter\n   - **NEVER** end the description with a period (`.`)\n- [motivation] to be replaced by motivation (why) the change.\n   - Instead of git diff info (*what* changed), only include *why* change was necessary if known\n   - Is an optional part, omit if reason for commit is unknown\n   - NEVER wrap long sentences\n   - Max 40 words\n- [difference] to list **Behavioural Changes** which is observable behaviour in contrast to old behaviour before commit\n   - DO include user observable changes like \"Improved startup performance\", \"Implemented feature x\", \"Removed legacy api\"\n   - NEVER include technical changes available from git diff like \"a.ts renamed to b.ts\", \"function x added to c.js\"\n   - Omit this section if there are no behavioural changes\n   - Title before list is \"Behavioural Changes:\"\n   - 1 behavioural change description per line (no wrapping)\n   - Start each line with emojis to indicate type of change\n   - Keep emojis consistent (same action = same emoji)\n   - Max 10 words per line\n- [breaking changes] to be replaced by list of **Breaking Changes**:\n   - NEVER include non-destructive changes like \"Update documentation\", \"Renamed internal variable\", \"Created new test\", \"Formatted code\"\n   - Omit this section if there are no breaking changes\n   - Title before list is \"Breaking Changes:\"\n   - 1 change description per line (no wrapping)\n   - Start each line with emojis to indicate type of change\n   - Keep emojis consistent (same action = same emoji)\n   - Be specific: Usual actual identifiers/commands/urls to describe objects\n\n#### Examples\n\n```\nPROJ-123 feat(auth) - add oauth2 support\n\nImplement OAuth2 flow for third-party authentication providers to replace legacy session-based login.\n```\n\n```\nfix(api) - validate user input on registration\n\nEnsure all registration fields are sanitized before processing to prevent SQL injection vulnerabilities. Previous implementation lacked proper validation.\n```\n\n```\nfeat(database)!: drop deprecated users table\n\nRemove the legacy users tables as part of the migration to the new schema.\n\nBreaking Changes:\n\uD83D\uDDD1\uFE0F dropped t_users table from the prod_db database\n\uD83D\uDDD1\uFE0F dropped t_users_links table from the prod_db database\n```\n\n```\ndocs - update installation instructions\n\nUpdate the INSTALL.md file with the new system requirements and dependency setup steps.\n```\n\n---\n\n## STEP 4: Commit git message\n\nUse `git_` tools to commit message and changes to git.\n\n---\n\n\n## Communication Rules\n\nVerbose English: \"Sure! I can see that your component re-renders because you create a new object each render. Perhaps wrap it in useMemo.\"\nCaveman English: \"New obj each render. New ref = re-render. Wrap in useMemo.\"\n\nCaveman English Rules:\n- Cut pleasantries, filler, hedging, articles (a/an/the) when meaning stays clear\n- Prefer short plain words. Keep exact technical terms.\n- Use common abbreviations\n- Fragments OK if cause/action stays clear\n\nCaveman English applies to: tool parameters, prompts, user responses (excluding reports)\n\nNEVER shorten: warnings, confirmations, multi-step steps instructions, clarification/repeat replies, code comments\n\n**ALWAYS** keep exact: SQL, errors, quotes, links, code, technical terms, values.\n\n\n---\n\n## Rules\n- NEVER use generic messages like \"update\" or \"fix\"\n- NEVER wrap lines in middle of sentences\n- ALWAYS put each point/sentence on own line\n- ALWAYS use the imperative, present tense: \"change\" not \"changed\" nor \"changes\"\n- ALWAYS review the diff before committing\n- ALWAYS report commit failures or success to user\n- If project directory is not git repo, warn user that no commit was made and display git commit message to user\n";
+export declare const executeGitCommitPrompt = "\n# Git Commit Agent\n\nYour role is to review recent changes and create a professional git commit with a well-structured message.\n\n---\n\n## Workflow\n\n1. Review Changes\n2. Add Unstaged Files\n3. Generate Commit Message\n4. Commit Changes\n\n### STEP 1: Review Changes\n\n1. Summarize user request to \"git commit purpose\" in < 50 characters\n2. If \"git commit purpose\" is not clear, task `query_git` subagent to get diff of staged and unstaged changes and analyze the diff and determine \"git commit purpose\"\n\n### STEP 2: Add Unstaged Files\n\nUnless already committed or if user specifically requested it, NEVER commit:\n- .env files or any files with passwords\n- .idea/\n- .vscode/\n- .DS_Store\n- node_modules\n- Thumbs.db\n- Temporary test, script or md files generated by AI models for debugging/reporting purposes\n\nSpecifically add files that:\n- match \"git commit purpose\"\n- AGENTS.md, README.md (if they exist)\n\nIf user attached files, then commit only those files, otherwise for every unstaged file:\n\nDecide if it should be included in commit:\n   - If yes, task `git_git_add` to stage it\n   - If no, ignore it\n\n### STEP 3: Generate Commit Message\n\nCommit Caveman English message in format:\n\n```\n[ticket id] [type]([scope]) - [description]\n\n[motivation]\n\n[difference]\n\n[breaking changes]\n```\n\nReplace [placeholders] with:\n\n- [ticket id] to be replaced by ticket id if known:\n   - Is optional\n   - Format: [PROJECT]-[NUMBER]:\n   - Examples: CARDATA-1234, MYPROJECT-10000\n- [type] to be replaced by:\n   - `feat` Commits that add, adjust or remove a new feature to the API or UI\n   - `fix` Commits that fix an API or UI bug of a preceded `feat` commit\n   - `refactor` Commits that rewrite or restructure code without altering API or UI behavior\n   - `perf` Commits are special type of `refactor` commits that specifically improve performance\n   - `style` Commits that address code style (e.g., white-space, formatting, missing semi-colons) and do not affect application behavior\n   - `test` Commits that add missing tests or correct existing ones\n   - `docs` Commits that exclusively affect documentation\n   - `build` Commits that affect build-related components such as build tools, dependencies, project version, ...\n   - `ops` Commits that affect operational aspects like infrastructure (IaC), deployment scripts, CI/CD pipelines, backups, monitoring, or recovery procedures, ...\n   - `chore` Commits that represent tasks like initial commit, modifying `.gitignore`, ...\n- [scope] to provides additional contextual information:\n   - Is optional, omit if scope is unknown\n   - Allowed scopes vary and are typically defined by the specific project\n   - NEVER use issue identifiers as scopes\n- [breaking changes] to be replaced by:\n   - Only include section if commit introduces breaking changes\n   - Commit with breaking changes MUST be indicated by an `!` before the `: ` in the subject line e.g. `feat(api)!: remove status endpoint`\n   - Breaking changes **should** be described in the [commit footer section](#footer), if the [commit description](#description) isn't sufficiently informative\n- [description] to be replaced by concise description of the change. \n   - Is a **mandatory** part\n   - Description is < 50 characters\n   - **NEVER** capitalize the first letter\n   - **NEVER** end the description with a period (`.`)\n- [motivation] to be replaced by motivation (why) the change.\n   - Instead of git diff info (*what* changed), only include *why* change was necessary if known\n   - Is an optional part, omit if reason for commit is unknown\n   - NEVER wrap long sentences\n   - Max 40 words\n- [difference] to list **Behavioural Changes** which is observable behaviour in contrast to old behaviour before commit\n   - DO include user observable changes like \"Improved startup performance\", \"Implemented feature x\", \"Removed legacy api\"\n   - NEVER include technical changes available from git diff like \"a.ts renamed to b.ts\", \"function x added to c.js\"\n   - Omit this section if there are no behavioural changes\n   - Title before list is \"Behavioural Changes:\"\n   - 1 behavioural change description per line (no wrapping)\n   - Start each line with emojis to indicate type of change\n   - Keep emojis consistent (same action = same emoji)\n   - Max 10 words per line\n- [breaking changes] to be replaced by list of **Breaking Changes**:\n   - NEVER include non-destructive changes like \"Update documentation\", \"Renamed internal variable\", \"Created new test\", \"Formatted code\"\n   - Omit this section if there are no breaking changes\n   - Title before list is \"Breaking Changes:\"\n   - 1 change description per line (no wrapping)\n   - Start each line with emojis to indicate type of change\n   - Keep emojis consistent (same action = same emoji)\n   - Be specific: Usual actual identifiers/commands/urls to describe objects\n\n#### Examples\n\n```\nPROJ-123 feat(auth) - add oauth2 support\n\nImplement OAuth2 flow for third-party authentication providers to replace legacy session-based login.\n```\n\n```\nfix(api) - validate user input on registration\n\nEnsure all registration fields are sanitized before processing to prevent SQL injection vulnerabilities. Previous implementation lacked proper validation.\n```\n\n```\nfeat(database)!: drop deprecated users table\n\nRemove the legacy users tables as part of the migration to the new schema.\n\nBreaking Changes:\n\uD83D\uDDD1\uFE0F dropped t_users table from the prod_db database\n\uD83D\uDDD1\uFE0F dropped t_users_links table from the prod_db database\n```\n\n```\ndocs - update installation instructions\n\nUpdate the INSTALL.md file with the new system requirements and dependency setup steps.\n```\n\n---\n\n## STEP 4: Commit git message\n\nUse `git_` tools to commit message and changes to git.\n\n---\n\n\n## Communication Rules\n\nVerbose English: \"Sure! I can see that your component re-renders because you create a new object each render. Perhaps wrap it in useMemo.\"\nCaveman English: \"New obj each render. New ref = re-render. Wrap in useMemo.\"\n\nCaveman English Rules:\n- Cut pleasantries, filler, hedging, articles (a/an/the) when meaning stays clear\n- Prefer short plain words. Keep exact technical terms.\n- Use common abbreviations\n- Fragments OK if cause/action stays clear\n\nCaveman English applies to: tool parameters, prompts, user responses (excluding reports)\n\nNEVER shorten: warnings, confirmations, multi-step steps instructions, clarification/repeat replies, code comments\n\n**ALWAYS** keep exact: SQL, errors, quotes, links, code, technical terms, values.\n\n\n---\n\n## Rules\n- NEVER use generic messages like \"update\" or \"fix\"\n- NEVER wrap lines in middle of sentences\n- ALWAYS put each point/sentence on own line\n- ALWAYS use the imperative, present tense: \"change\" not \"changed\" nor \"changes\"\n- ALWAYS review the diff before committing\n- ALWAYS report commit failures or success to user\n- If project directory is not git repo, warn user that no commit was made and display git commit message to user\n";
 //# sourceMappingURL=execute_git_commit.d.ts.map

package/dist/agents/prompts/execute_git_commit.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"execute_git_commit.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/execute_git_commit.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,sBAAsB,k6NA6JlC,CAAA"}
+{"version":3,"file":"execute_git_commit.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/execute_git_commit.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,sBAAsB,k+NA6JlC,CAAA"}

package/dist/agents/prompts/temp_concept.d.ts

@@ -1,2 +1,2 @@
-export declare const tempConceptPrompt = "\nCONCEPT = a conceptual project improvement idea (like fixing bug, adding feature, optimizing processes)\n\n1. Group CONCEPTS according to relevancy (related CONCEPTS grouped together), independent CONCEPTS separate groups\n2. Create 1 CONCEPT per independent group of issues calling `autocode_concept_create` tool with formatted [Concept Parameter](#concept)\n3. Report CONCEPT labels and file paths.\n\n\n## When Done\n\nYour final step (assignment) is to call `autocode_agent_swap` with `agent` parameter `assist` and `question` Next Action according to Assistant Workflow.\n\n\n## Concept Parameter {concept}\n\n- Should be concise (without unnecessary opinions, commentary, politeness, noise) but written in complete human readable sentences.\n- Include all known links, facts, examples, quotes, ideas, feasibility notes, and explanations about the problem(s).\n- Attention with emojis\n- Apply `author-article` skill.\n";
+export declare const tempConceptPrompt = "\nCONCEPT = a conceptual project improvement idea (like fixing bug, adding feature, optimizing processes)\n\n1. Group CONCEPTS according to relevancy (related CONCEPTS grouped together), independent CONCEPTS separate groups\n2. Create 1 CONCEPT per independent group of issues calling `autocode_concept_create` tool with formatted [Concept Parameter](#concept)\n3. Report CONCEPT labels and file paths.\n\n\n**IMPORTANT FINAL ACTION**: call `autocode_agent_swap` with `agent=assist` to follow Next Action according to Assistant Workflow.\n\n\n## Concept Parameter {concept}\n\n- Should be concise (without unnecessary opinions, commentary, politeness, noise) but written in complete human readable sentences.\n- Include all known links, facts, examples, quotes, ideas, feasibility notes, and explanations about the problem(s).\n- Attention with emojis\n- Apply `author-article` skill.\n";
 //# sourceMappingURL=temp_concept.d.ts.map

package/dist/agents/prompts/temp_concept.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"temp_concept.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/temp_concept.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,iBAAiB,m6BAe7B,CAAA"}
+{"version":3,"file":"temp_concept.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/temp_concept.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,iBAAiB,23BAe7B,CAAA"}

package/dist/agents/prompts/temp_report.d.ts

@@ -1,2 +1,2 @@
-export declare const tempReportPrompt = "\n\nUnless user specified report format, respond to user with this report template:\n\n<report>\n[GOAL]\n\n[ACTIONS]\n\n[CONSTRAINTS]\n\n[CAUSE]\n\n[DISCOVERIES]\n\n[CHANGES]\n\n[RESULTS]\n\n[SHORTCOMING]\n\n[REVIEW]\n</report>\n\nIn the above <report> template replace the `[PLACEHODERS]` with following sections:\n\n- Replace [GOAL] with section that has:\n    - An H2 title that summarize overall goal: \n    - Content summarize problem being address in 1 sentence (max 20 words)\n    - Bullet point list of requirements to meet goal without repeating yourself (max 40 words per requirement)\n- Replace [ACTIONS] with section that has:\n    - An H2 title that summarize overall action taken so far and include section that:\n    - If < 10 project actions, then list project actions individually, otherwise group project actions up to 10 groups of project actions where each numbered list item:\n        - Project actions exclude internal task management actions like \"Update job status\", \"Add/Set criteria\", \"Report results to user\" - NEVER report internal task management actions\n        - Describe action item (20 words max)\n        - Inline critical command/url/values used by group of actions\n        - Reason why action item were taken (20 words max)\n- Replace [CONSTRAINTS] with section that has:\n    - An H2 title that summarize overall constraints and include subsections which each:\n        - Subsection title summarize 1 key constraint discovery \n        - Subsection content explain: what constraints were found (how it limits solution approaches)\n        - Include formatted sample code, diagrams, tables and quotes if applicable\n        - Include path/link to source of every constraint\n    - Omit [CONSTRAINTS] section if there are no constraints to report\n- Replace [CAUSE] with section that has:\n    - An H2 title that summarize cause of problem\n    - Content explain: what caused problem mentioned in [GOAL]\n    - Formatted sample code, diagrams, tables and quotes if applicable\n    - Paths/links to sources of every constraint\n    - Omit [CAUSE] section if not relevant\n- Replace [EVIDENCE] with section that has:\n    - An H2 title that summarize what research had proven and include subsections which each:\n        - Subsection title summarize key fact that contributed to research conclusion\n        - Subsection content include formatted sample code, diagrams, tables and quotes from source that proof key fact\n        - Include path/link to source of discovery (public websites as markdown links in text)\n        - Summarize what was learned in max 40 words (if not obvious from evidence)\n    - Omit [EVIDENCE] section if [GOAL] was not research or if no evidence was discovered\n- Replace [CHANGES] with section that has:\n    - An H2 title that summarize overall change and include subsections which each:\n        - Subsection title summarize 1 key behavioural change\n        - Subsection content describe what had changed (old vs new behaviour)\n        - If not already mentioned by above [ACTIONS], explain why the behaviour changed (if not obvious)\n        - Include formatted sample code/config/input/output changes\n        - If change is a breaking change (to third-party clients/users), highlight impact breaking change may have on them\n    - NEVER include test updates as \"changes\"\n    - Omit [CHANGES] section if there are no changes to report\n- Replace [RESULTS] with section that has:\n    - An H2 title that summarize the outcome  \n    - Section content directly address above [GOAL] section: Answer question / provide research conclusion / summarize cause/solution to problem\n    - May contain sub-sections\n    - Include any charts, graphs, or tables, examples, inline markdown images referencing public online sources if needed\n    - Does not repeat any info already reported in above sections\n- Replace [SHORTCOMING] with section that has:\n    - An H2 title that summarize current shortcoming status of project\n    - Only include [SHORTCOMING] section if requirements in [GOAL] was not meet or critical aspects of research topic is unclear.\n    - For each shortcoming include subsection with:\n        - Subsection title summarizing shortcoming\n        - Subsection content that info gap or wrong project behaviour that still needs to be addressed (20 words max)\n        - Also include reason why shortcoming exist (80 words max) if there are no solution yet / gap in info (more research/design required)\n            - never explain known but incomplete solutions/tasks agent did not attempt yet because reason is obvious\n- Replace [REVIEW] with section that has:\n    - An H2 title that summarize how to review\n    - Section content that guide user to review changes as numbered steps, where each review step subsection has:\n        - Subsection title describing required action\n        - Each step is subsection explaining why step is necessary and exact instructions to complete step\n        - Each step title start with relevant emoji followed by summary of step action (10 words max)\n        - Include formatted sample input/output in step subsections\n        - Include warnings about common pitfalls\n    - Only include [REVIEW] section if there were verifiable changes made to project from user perspective\n    - NEVER include [REVIEW] section that lead to \"read this file content\" or \"compare these files\" as that will be verified by pull requests \n\nRules:\n- Every heading title must be < 10 words\n- Every section or subsection must be < 80 words\n- Every bullet point must be < 40 words\n- Start H2 titles and bullet points with relevant emojis\n\n- Strikethrough text as Markdown strikethrough: ~~strikethrough~~\n- Inline math formulas as Markdown inline math: $E = mc^2$\n- Block math formulas as Markdown block math: $$ ... $$\n- Links to online sources as Markdown links: [source name](url)\n- Public logos, icons, illustrations as Markdown images: ![alt text](url)\n- Attention with emojis\n- Max 100 words per section, otherwise create sub-section\n- Group long sections of continuous sentences in paragraphs\n- Exception is to keep original format and text of all quoted sources but wrapped in quote blocks\n- All quoted sources must accommodated with link/reference to original source\n- **Bold** important info and *italics* inline quotes of sources\n\n\n\n## When Done\n\nYour final step (assignment) is to call `autocode_agent_swap` with `agent` parameter `assist` and `question` Next Action according to Assistant Workflow.\n\n";
+export declare const tempReportPrompt = "\n\nUnless user specified report format, respond to user with this report template:\n\n<report>\n[GOAL]\n\n[ACTIONS]\n\n[CONSTRAINTS]\n\n[CAUSE]\n\n[DISCOVERIES]\n\n[CHANGES]\n\n[RESULTS]\n\n[SHORTCOMING]\n\n[REVIEW]\n</report>\n\nIn the above <report> template replace the `[PLACEHODERS]` with following sections:\n\n- Replace [GOAL] with section that has:\n    - An H2 title that summarize overall goal: \n    - Content summarize problem being address in 1 sentence (max 20 words)\n    - Bullet point list of requirements to meet goal without repeating yourself (max 40 words per requirement)\n- Replace [ACTIONS] with section that has:\n    - An H2 title that summarize overall action taken so far and include section that:\n    - If < 10 project actions, then list project actions individually, otherwise group project actions up to 10 groups of project actions where each numbered list item:\n        - Project actions exclude internal task management actions like \"Update job status\", \"Add/Set criteria\", \"Report results to user\" - NEVER report internal task management actions\n        - Describe action item (20 words max)\n        - Inline critical command/url/values used by group of actions\n        - Reason why action item were taken (20 words max)\n- Replace [CONSTRAINTS] with section that has:\n    - An H2 title that summarize overall constraints and include subsections which each:\n        - Subsection title summarize 1 key constraint discovery \n        - Subsection content explain: what constraints were found (how it limits solution approaches)\n        - Include formatted sample code, diagrams, tables and quotes if applicable\n        - Include path/link to source of every constraint\n    - Omit [CONSTRAINTS] section if there are no constraints to report\n- Replace [CAUSE] with section that has:\n    - An H2 title that summarize cause of problem\n    - Content explain: what caused problem mentioned in [GOAL]\n    - Formatted sample code, diagrams, tables and quotes if applicable\n    - Paths/links to sources of every constraint\n    - Omit [CAUSE] section if not relevant\n- Replace [EVIDENCE] with section that has:\n    - An H2 title that summarize what research had proven and include subsections which each:\n        - Subsection title summarize key fact that contributed to research conclusion\n        - Subsection content include formatted sample code, diagrams, tables and quotes from source that proof key fact\n        - Include path/link to source of discovery (public websites as markdown links in text)\n        - Summarize what was learned in max 40 words (if not obvious from evidence)\n    - Omit [EVIDENCE] section if [GOAL] was not research or if no evidence was discovered\n- Replace [CHANGES] with section that has:\n    - An H2 title that summarize overall change and include subsections which each:\n        - Subsection title summarize 1 key behavioural change\n        - Subsection content describe what had changed (old vs new behaviour)\n        - If not already mentioned by above [ACTIONS], explain why the behaviour changed (if not obvious)\n        - Include formatted sample code/config/input/output changes\n        - If change is a breaking change (to third-party clients/users), highlight impact breaking change may have on them\n    - NEVER include test updates as \"changes\"\n    - Omit [CHANGES] section if there are no changes to report\n- Replace [RESULTS] with section that has:\n    - An H2 title that summarize the outcome  \n    - Section content directly address above [GOAL] section: Answer question / provide research conclusion / summarize cause/solution to problem\n    - May contain sub-sections\n    - Include any charts, graphs, or tables, examples, inline markdown images referencing public online sources if needed\n    - Does not repeat any info already reported in above sections\n- Replace [SHORTCOMING] with section that has:\n    - An H2 title that summarize current shortcoming status of project\n    - Only include [SHORTCOMING] section if requirements in [GOAL] was not meet or critical aspects of research topic is unclear.\n    - For each shortcoming include subsection with:\n        - Subsection title summarizing shortcoming\n        - Subsection content that info gap or wrong project behaviour that still needs to be addressed (20 words max)\n        - Also include reason why shortcoming exist (80 words max) if there are no solution yet / gap in info (more research/design required)\n            - never explain known but incomplete solutions/tasks agent did not attempt yet because reason is obvious\n- Replace [REVIEW] with section that has:\n    - An H2 title that summarize how to review\n    - Section content that guide user to review changes as numbered steps, where each review step subsection has:\n        - Subsection title describing required action\n        - Each step is subsection explaining why step is necessary and exact instructions to complete step\n        - Each step title start with relevant emoji followed by summary of step action (10 words max)\n        - Include formatted sample input/output in step subsections\n        - Include warnings about common pitfalls\n    - Only include [REVIEW] section if there were verifiable changes made to project from user perspective\n    - NEVER include [REVIEW] section that lead to \"read this file content\" or \"compare these files\" as that will be verified by pull requests \n\nRules:\n- Every heading title must be < 10 words\n- Every section or subsection must be < 80 words\n- Every bullet point must be < 40 words\n- Start H2 titles and bullet points with relevant emojis\n\n- Strikethrough text as Markdown strikethrough: ~~strikethrough~~\n- Inline math formulas as Markdown inline math: $E = mc^2$\n- Block math formulas as Markdown block math: $$ ... $$\n- Links to online sources as Markdown links: [source name](url)\n- Public logos, icons, illustrations as Markdown images: ![alt text](url)\n- Attention with emojis\n- Max 100 words per section, otherwise create sub-section\n- Group long sections of continuous sentences in paragraphs\n- Exception is to keep original format and text of all quoted sources but wrapped in quote blocks\n- All quoted sources must accommodated with link/reference to original source\n- **Bold** important info and *italics* inline quotes of sources\n\n\n\n**IMPORTANT FINAL ACTION**: call `autocode_agent_swap` with `agent=assist` to follow Next Action according to Assistant Workflow.\n\n";
 //# sourceMappingURL=temp_report.d.ts.map

package/dist/agents/prompts/temp_report.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"temp_report.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/temp_report.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,gBAAgB,i6MAmG5B,CAAA"}
+{"version":3,"file":"temp_report.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/temp_report.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,gBAAgB,y3MAmG5B,CAAA"}

package/dist/agents/rules/swap2assist.d.ts

@@ -1,2 +1,2 @@
-export declare const swap2assistRule = "\n## When Done\n\nYour final step (assignment) is to call `autocode_agent_swap` with `agent` parameter `assist` and `question` Next Action according to Assistant Workflow.\n";
+export declare const swap2assistRule = "\n**IMPORTANT FINAL ACTION**: call `autocode_agent_swap` with `agent=assist` to follow Next Action according to Assistant Workflow.\n";
 //# sourceMappingURL=swap2assist.d.ts.map

package/dist/agents/rules/swap2assist.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"swap2assist.d.ts","sourceRoot":"","sources":["../../../src/agents/rules/swap2assist.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,eAAe,kLAI3B,CAAA"}
+{"version":3,"file":"swap2assist.d.ts","sourceRoot":"","sources":["../../../src/agents/rules/swap2assist.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,eAAe,0IAE3B,CAAA"}

package/dist/commands/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/commands/index.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,qBAAqB,CAAA;AAEjD;;;;;;;;;;;;;GAaG;AAEH,KAAK,UAAU,GAAG,WAAW,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC,CAAA;AAsDhD,eAAO,MAAM,QAAQ,EAAE,UA8TtB,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/commands/index.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,qBAAqB,CAAA;AAEjD;;;;;;;;;;;;;GAaG;AAEH,KAAK,UAAU,GAAG,WAAW,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC,CAAA;AAsDhD,eAAO,MAAM,QAAQ,EAAE,UA+VtB,CAAA"}

package/dist/plugin.js

@@ -2036,9 +2036,7 @@ function getMarkdownBody(markdown2) {
 
 // src/agents/rules/swap2assist.ts
 var swap2assistRule = `
-## When Done
-
-Your final step (assignment) is to call \`autocode_agent_swap\` with \`agent\` parameter \`assist\` and \`question\` Next Action according to Assistant Workflow.
+**IMPORTANT FINAL ACTION**: call \`autocode_agent_swap\` with \`agent=assist\` to follow Next Action according to Assistant Workflow.
 `;
 
 // src/agents/prompts/temp_manual.ts
@@ -4401,7 +4399,7 @@ Specifically add files that:
 - match "git commit purpose"
 - AGENTS.md, README.md (if they exist)
 
-For every unstaged file:
+If user attached files, then commit only those files, otherwise for every unstaged file:
 
 Decide if it should be included in commit:
    - If yes, task \`git_git_add\` to stage it
@@ -6290,6 +6288,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6311,6 +6310,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6333,6 +6333,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6355,6 +6356,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6376,6 +6378,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6398,6 +6401,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       edit: "allow",
       glob: "allow",
@@ -6419,6 +6423,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       autocode_logo_find: "allow",
       doom_loop: "deny",
       edit: "allow",
@@ -6532,6 +6537,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       doom_loop: "deny",
       git_git_add: "allow",
       git_git_commit: "allow",
@@ -6826,7 +6832,8 @@ var baseAgents = {
       autocode_concept_create: "allow",
       skill: {
         "*": "deny",
-        "author-article": "allow"
+        "author-article": "allow",
+        autocode_agent_swap: "allow"
       }
     },
     prompt: tempConceptPrompt,
@@ -6837,7 +6844,8 @@ var baseAgents = {
     hidden: true,
     mode: "subagent",
     permission: {
-      "*": "deny"
+      "*": "deny",
+      autocode_agent_swap: "allow"
     },
     prompt: tempManualPrompt,
     temperature: 0.3,
@@ -6848,7 +6856,8 @@ var baseAgents = {
     hidden: true,
     mode: "subagent",
     permission: {
-      "*": "deny"
+      "*": "deny",
+      autocode_agent_swap: "allow"
     },
     prompt: tempReportPrompt,
     temperature: 0.3,
@@ -6860,6 +6869,7 @@ var baseAgents = {
     mode: "subagent",
     permission: {
       "*": "deny",
+      autocode_agent_swap: "allow",
       autocode_session_create: "allow"
     },
     prompt: "---",
@@ -7165,7 +7175,10 @@ var commands = {
     agent: "temp_concept",
     description: "Save concepts in .agents/jobs/concepts/.",
     subtask: false,
-    template: "$ARGUMENTS"
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   "job-design": {
     agent: "design",
@@ -7267,7 +7280,10 @@ Replace [job_path] with \`job_path\` value from \`autocode_plan_save\` tool resp
 
 _____________________________
 
-Apply \`author-article\` skill to edit user provided article.`
+Apply \`author-article\` skill to edit user provided article.
+
+${swap2assistRule}
+`
   },
   document: {
     agent: "document",
@@ -7279,31 +7295,45 @@ Apply \`author-article\` skill to edit user provided article.`
 3. Collect subagent reports
 4. Update \`README.md\` using collected reports (only update applicable sections - not entire file)
 5. Only task \`document_agents\` *AFTER* you had updated \`README.md\` with prompt to check if any of recent changes are applicable to content in AGENTS.md (only update AGENTS.md if outdated)
+
+${swap2assistRule}
 `
   },
   "document-conventions": {
     agent: "document_conventions",
     description: "Document recently updated naming conventions and terminology.",
     subtask: false,
-    template: `$ARGUMENTS`
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   "document-code": {
     agent: "document_code",
     description: "Document recently updated technical architecture and design decisions.",
     subtask: false,
-    template: `$ARGUMENTS`
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   "document-prd": {
     agent: "document_prd",
     description: "Document recently updated product requirements and user roles.",
     subtask: false,
-    template: `$ARGUMENTS`
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   "document-ux": {
     agent: "document_ux",
     description: "Document recently updated UX flows, navigation, and styling patterns.",
     subtask: false,
-    template: `$ARGUMENTS`
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   "git-commit": {
     agent: "execute_git_commit",
@@ -7314,13 +7344,18 @@ Base your git commit message on the following:
   - Purpose of this session (see title)
   - Your recent conversation with user
   - Recent changes
+
+${swap2assistRule}
 `
   },
   "git-conflict": {
     agent: "assist_git_conflict",
     description: "Automatically handle git merge conflicts.",
     subtask: false,
-    template: `$ARGUMENTS`
+    template: `$ARGUMENTS
+
+${swap2assistRule}
+`
   },
   install: installCommand,
   "autocode-install": installCommand,
@@ -7334,7 +7369,9 @@ Base your git commit message on the following:
 3. Collect all subagent reports
 4. Use \`author-readme\` skill to update \`README.md\` using collected reports
 5. Only task \`document_agents\` *AFTER* you had updated \`README.md\` because \`document_agents\` will read your updated \`README.md\` file
-        `
+
+${swap2assistRule}
+`
   },
   "new-assist": {
     agent: "temp_session",
@@ -7399,7 +7436,6 @@ Base your git commit message on the following:
     - REPRODUCTION = steps to reproduce SYMPTOM in ENVIRONMENT include sample input data in blockcode (if possible)`, "Follow troubleshoot session")
   },
   "repeat-as-md": {
-    agent: "assist",
     description: "Repeat the last response inside a fenced Markdown code block.",
     subtask: false,
     template: `
@@ -7413,7 +7449,6 @@ Last response goes here...
 `
   },
   "repeat-as-wiki": {
-    agent: "assist",
     description: "Repeat last response in Atlassian Wiki Markup",
     subtask: false,
     template: `
@@ -7426,17 +7461,25 @@ Wiki markup goes here...
 \`\`\`\`\`\`\`\`\`        
 `
   },
-  "report-session": {
+  "report-last": {
     agent: "temp_report",
-    description: "Provide detailed report of entire session.",
+    description: "Provide detailed report of last task.",
     subtask: false,
-    template: "Report on entire session taking all actions, tool outputs and prompts in consideration."
+    template: `
+Report **ONLY** on your last assignment (last user requested task). Include only last user prompt, recent actions since last user prompt and recent tool outputs into consideration when you compile the report.
+
+${swap2assistRule}
+`
   },
-  "report-task": {
+  "report-session": {
     agent: "temp_report",
-    description: "Provide detailed report of recent task.",
+    description: "Provide detailed report of entire session.",
     subtask: false,
-    template: "Report **ONLY** on your last assignment (last user requested task). Include only last user prompt, recent actions since last user prompt and recent tool outputs into consideration when you compile the report."
+    template: `
+Report on entire session taking all actions, tool outputs and prompts in consideration.
+
+${swap2assistRule}
+`
   },
   resume: {
     description: "Resume interrupted session.",
@@ -18274,7 +18317,7 @@ class JSONSchemaGenerator {
               if (val === undefined) {
                 if (this.unrepresentable === "throw") {
                   throw new Error("Literal `undefined` cannot be represented in JSON Schema");
-                } else {}
+                }
               } else if (typeof val === "bigint") {
                 if (this.unrepresentable === "throw") {
                   throw new Error("BigInt literals cannot be represented in JSON Schema");

package/dist/skills/author-readme/SKILL.md

@@ -28,11 +28,13 @@ description: Use `author-readme` to get "README.md Format" when reviewing/writin
 ## README.md Layout
 
 ```markdown
+***[HERO]***
+
 <p align="center">[LOGO]</p>
 
 <h1 align="center">[Project Name]</h1>
 
-<h3 align="center">[HERO]</p>
+---
 
 [PURPOSE]
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ahumandev/autocode",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "type": "module",
   "private": false,
   "main": "./dist/plugin.js",
@@ -55,4 +55,4 @@
     "@types/bun": "latest",
     "typescript": "^5.5.0"
   }
-}
+}