feat(workflows): expand template library from 9 to 22 + multiline string cleanup#36
Merged
feat(workflows): expand template library from 9 to 22 + multiline string cleanup#36
Conversation
…ss, and productivity Engineering: - bug-triage: reproduce path → root cause → fix plan - api-design: resource model → endpoints → OpenAPI spec - incident-postmortem: timeline → RCA → full postmortem report - test-generation: code analysis → edge cases → full test suite - refactor-plan: smell analysis → prioritised opportunities → migration plan Business: - competitor-analysis: profiles → SWOT → strategy report - product-spec: problem definition → user stories → full PRD - market-research: landscape → segments → research report Productivity/Thinking: - meeting-summary: raw notes → structured summary → follow-up email - decision-matrix: criteria → weighted scoring → recommendation memo - learning-plan: gap analysis → roadmap → week-1 day-by-day plan - job-application: job analysis → tailored resume → cover letter → interview prep - blog-post: research → outline → draft → SEO optimisation Closes #1912 on librefang/librefang
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
- data-pipeline: redesigned — original 'extract from URL' step was broken (LLMs cannot fetch URLs); replaced with paste-data approach (profile → clean_transform → analyse) with analysis_goal parameter - translate-polish: added target_language and register parameters; added back-translation step for accuracy verification - weekly-report: added team/audience parameters, richer extraction step, added Metrics and Notes sections - content-pipeline: added audience/tone parameters, added outline step between research and writing - content-review: fix category 'content' → 'creation' - customer-support: fix category 'support' → 'business'
…ne syntax
Replace \n escape sequences with real newlines using triple-quote
multiline strings ("""...""") across all 22 workflow templates.
No content changes — formatting only.
houko
changed the title
…multiline code block
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.
Summary
\nescape sequences in prompt strings to TOML multiline syntax ("""...""") across the entire repoNew Templates
Engineering:
test-generation,refactor-plan,api-design,bug-triage,incident-postmortemBusiness:
market-research,competitor-analysis,product-spec,decision-matrixProductivity:
meeting-summary,learning-plan,job-application,blog-postExisting Template Improvements
data-pipelineraw_dataparam;profile → clean_transform → analyseDAGtranslate-polishtarget_language+registerparams; addedback_translateaccuracy stepweekly-reportteam_or_role+audienceparams; added Metrics and Notes sectionscontent-pipelineaudience+toneparams; addedoutlinestep; 4-step DAGcontent-reviewcreation); added platform-specific tone guidancecustomer-supportbusiness); added empathy and escalation stepstest-generationlanguageparam;code_analysis → edge_cases → test_suiteDAGrefactor-plancontextparam;smell_analysis → prioritised_opportunities → migration_planDAGmarket-researchbusiness_contextparam;market_landscape → customer_segments → research_reportDAG