feat(workflows): add new workflow files and update READMEs#1
Merged
Conversation
- Add new workflow files for code review, refactoring, testing and documentation - Update README files with detailed workflow descriptions - Add gitignore files for project and tools directories - Add yarn.lock for tools dependencies
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
7 issues found across 15 files
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="workflows/documentation/README.md">
<violation number="1" location="workflows/documentation/README.md:6">
P2: Broken link: the file `api-docs-gen.mwc.yaml` does not exist. The actual file is named `api-docs-generator.mwc.yaml`.</violation>
</file>
<file name="workflows/refactoring/performance-audit.mwc.yaml">
<violation number="1" location="workflows/refactoring/performance-audit.mwc.yaml:22">
P1: The `suggest_optimizations` step claims to use the complexity and leak analysis but doesn't reference those step outputs. Without injecting `{{analyze_complexity}}` and `{{find_leaks}}`, the model won't have access to the actual analysis results to base its suggestions on.</violation>
</file>
<file name="workflows/documentation/i18n-extractor.mwc.yaml">
<violation number="1" location="workflows/documentation/i18n-extractor.mwc.yaml:21">
P1: Missing step chaining: `generate_keys` should reference `{{find_strings}}` to know which strings need i18n keys. Without this, the step has no context from the previous step's output.</violation>
<violation number="2" location="workflows/documentation/i18n-extractor.mwc.yaml:25">
P1: Missing step chaining: `suggest_replacements` should reference `{{generate_keys}}` (and optionally `{{find_strings}}`) to know what i18n keys to use in code replacements.</violation>
</file>
<file name="workflows/documentation/readme-optimizer.mwc.yaml">
<violation number="1" location="workflows/documentation/readme-optimizer.mwc.yaml:21">
P1: The prompt references `{{analyze_gaps}}` but is missing `{{current_readme}}`. The model cannot rewrite the README without access to the original content.</violation>
</file>
<file name="workflows/code-review/bug-fixer.mwc.yaml">
<violation number="1" location="workflows/code-review/bug-fixer.mwc.yaml:21">
P1: Step `propose_fix` should reference `{{analyze_error}}` to include the analysis result. Without this template reference, the step won't have access to the previous step's output.</violation>
<violation number="2" location="workflows/code-review/bug-fixer.mwc.yaml:25">
P2: Step `verify_fix` should reference `{{propose_fix}}` to include the proposed fix in the verification prompt.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
…ains Add README files and workflow templates for 30+ domains including DevOps, SRE, Database, Product, DevEx, Legal, Data Science, LLM Ops, Cloud Native, QA Automation, Cybersecurity, Marketing, Blockchain, Game Dev, FinOps, Compliance, Mobile, Spatial Computing, Technical Writing, Embedded, Open Source, Management, UX/UI, and more. Each workflow includes: - README with domain overview and workflow list - YAML templates for common tasks in the domain - Input/output definitions and step-by-step prompts - Support for multiple languages and frameworks Also add audit_depth.js tool to analyze workflow complexity and prompt quality.
Contributor
There was a problem hiding this comment.
25 issues found across 108 files (changes from recent commits).
Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="workflows/management/README.md">
<violation number="1" location="workflows/management/README.md:7">
P2: Broken link: `1-on-1-meeting.mwc.yaml` does not exist in the `workflows/management` directory. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="workflows/legacy-migration/db-migrator.mwc.yaml">
<violation number="1" location="workflows/legacy-migration/db-migrator.mwc.yaml:11">
P2: Workflow step doesn't match the declared output. The `map_data` step only creates a mapping, but the output promises `migration_scripts`. Consider adding a second step to generate actual SQL/NoSQL migration scripts from the mapping.</violation>
</file>
<file name="workflows/api-economy/api-versioning-plan.mwc.yaml">
<violation number="1" location="workflows/api-economy/api-versioning-plan.mwc.yaml:6">
P2: The `current_version` input is defined but never used in the workflow. For an API versioning plan, knowing the current version is critical context. Consider using it in the prompt, e.g., `Currently at version {{current_version}}, design a versioning strategy...`</violation>
</file>
<file name="workflows/devops/README.md">
<violation number="1" location="workflows/devops/README.md:6">
P2: Broken link: `ci-pipeline-gen.mwc.yaml` does not exist in the devops directory. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="workflows/finops/README.md">
<violation number="1" location="workflows/finops/README.md:6">
P2: Broken link: `tagging-audit.mwc.yaml` is referenced but does not exist in this directory. Either add the missing workflow file or remove this line from the README.</violation>
</file>
<file name="workflows/cloud-native/k8s-manifest-gen.mwc.yaml">
<violation number="1" location="workflows/cloud-native/k8s-manifest-gen.mwc.yaml:25">
P2: Missing step to combine outputs from `generate_deployment` and `generate_networking` into the `k8s_manifests` output. Consider adding a format or aggregation step that references both step outputs.</violation>
</file>
<file name="workflows/devex/README.md">
<violation number="1" location="workflows/devex/README.md:6">
P2: Broken link: `rfc-generator.mwc.yaml` is referenced but the file does not exist in the repository. Either add the missing workflow file or remove this entry from the README.</violation>
</file>
<file name="workflows/embedded/README.md">
<violation number="1" location="workflows/embedded/README.md:6">
P2: Broken link: `embedded-mem-audit.mwc.yaml` does not exist in the `workflows/embedded/` directory. Either add the missing workflow file or remove this reference from the README.</violation>
</file>
<file name="workflows/game-dev/README.md">
<violation number="1" location="workflows/game-dev/README.md:6">
P2: Broken link: `mechanic-designer.mwc.yaml` is referenced but does not exist in the repository. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="workflows/cybersecurity/README.md">
<violation number="1" location="workflows/cybersecurity/README.md:6">
P2: Broken link: `vuln-scanner.mwc.yaml` does not exist in the cybersecurity workflows directory. Either create the missing workflow file or remove this reference.</violation>
</file>
<file name="workflows/database/README.md">
<violation number="1" location="workflows/database/README.md:6">
P2: Broken link: `schema-designer.mwc.yaml` is referenced but does not exist in the repository. Either add the missing workflow file or remove this reference.</violation>
</file>
<file name="workflows/e-commerce/product-seo-gen.mwc.yaml">
<violation number="1" location="workflows/e-commerce/product-seo-gen.mwc.yaml:7">
P2: Missing required `description` field for input `product_specs`. The MWC specification requires all inputs to have `name`, `type`, and `description` fields.</violation>
</file>
<file name="workflows/data-science/data-pipeline-gen.mwc.yaml">
<violation number="1" location="workflows/data-science/data-pipeline-gen.mwc.yaml:21">
P1: The transformation step references "the extraction logic" but doesn't include a variable reference to the output of `generate_extraction`. The prompt only uses `{{transformations}}` from inputs, so the model won't receive the extraction code generated in step 1. Consider adding something like `{{generate_extraction}}` to pass the previous step's output.</violation>
</file>
<file name="workflows/architecture/README.md">
<violation number="1" location="workflows/architecture/README.md:6">
P2: Broken link: `module-generator.mwc.yaml` does not exist in this directory. Either add the missing workflow file or remove this reference from the README.</violation>
</file>
<file name="workflows/blockchain/README.md">
<violation number="1" location="workflows/blockchain/README.md:6">
P2: Broken link: `dapp-scaffolder.mwc.yaml` is referenced but does not exist in the `workflows/blockchain/` directory. Either add the missing workflow file or remove this line from the README.</violation>
</file>
<file name="workflows/llm-ops/README.md">
<violation number="1" location="workflows/llm-ops/README.md:6">
P2: Broken link: `model-eval-gen.mwc.yaml` does not exist in the `workflows/llm-ops/` directory. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="workflows/llm-ops/prompt-optimizer.mwc.yaml">
<violation number="1" location="workflows/llm-ops/prompt-optimizer.mwc.yaml:21">
P1: Step `add_examples` doesn't reference the output of `apply_cot`, so the Chain-of-Thought improvements from step 1 are lost. The prompt should include `{{apply_cot}}` to chain the steps together properly.</violation>
</file>
<file name="workflows/compliance/README.md">
<violation number="1" location="workflows/compliance/README.md:6">
P2: Broken link: `privacy-policy-gen.mwc.yaml` does not exist in the `workflows/compliance/` directory. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="workflows/data-science/README.md">
<violation number="1" location="workflows/data-science/README.md:6">
P2: Broken link: `dataset-sum.mwc.yaml` does not exist in the repository. Either add the missing workflow file or update the link to reference an existing file.</violation>
</file>
<file name="workflows/marketing-growth/README.md">
<violation number="1" location="workflows/marketing-growth/README.md:6">
P2: Broken link: `ad-copy-gen.mwc.yaml` does not exist in this directory. Either add the missing workflow file or update the link to reference an existing workflow (e.g., `landing-page-wireframe.mwc.yaml` which exists but isn't documented).</violation>
</file>
<file name="workflows/customer-support/kb-auditor.mwc.yaml">
<violation number="1" location="workflows/customer-support/kb-auditor.mwc.yaml:11">
P2: The workflow description promises to check for "broken links" but the prompt doesn't implement this functionality. Either update the description to match what the prompt does, or update the prompt to include broken link detection.</violation>
</file>
<file name="workflows/legal/README.md">
<violation number="1" location="workflows/legal/README.md:6">
P2: Broken link: `gdpr-checklist.mwc.yaml` is referenced but does not exist in the workflows/legal directory. Either add the missing workflow file or remove this link from the README.</violation>
</file>
<file name="README.md">
<violation number="1" location="README.md:25">
P2: Inaccurate workflow count: The README claims 105 workflows but there are only 97 `.mwc.yaml` files in the repository. Consider updating to the correct count or using a dynamic approach to avoid this becoming stale.</violation>
</file>
<file name="workflows/cloud-native/README.md">
<violation number="1" location="workflows/cloud-native/README.md:5">
P2: Broken link: `k8s-manifest-gen.mwc.yaml` does not exist in the `workflows/cloud-native/` directory. Either add the referenced workflow file or remove this link from the README.</violation>
<violation number="2" location="workflows/cloud-native/README.md:6">
P2: Broken link: `helm-scaffolder.mwc.yaml` does not exist in the `workflows/cloud-native/` directory. Either add the referenced workflow file or remove this link from the README.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
- Remove deprecated workflows from README files across categories - Add missing descriptions and improve prompt references in workflow files - Update workflow count in main README to reflect current state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Briefly describe the changes in this PR.
Type of Change
Checklist
node tools/validator.js.Summary by cubic
Added 100+ MWC workflows across 30+ domains with updated READMEs for easy discovery, plus a deep audit report. Also adds root and tools .gitignore files, an audit tool, and pins tool dependencies with a yarn.lock.
New Features
Dependencies
Written for commit 4df7a67. Summary will update on new commits.