[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ANYQKRW4XFHMHK9ZDNWHY3":3,"skill-same:01M7ANYQKRW4XFHMHK9ZDNWHY3":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ANYQKRW4XFHMHK9ZDNWHY3","ghjira-integration-metrics-and-anti-patterns",null,"Use when wiring GitHub and Jira together or deciding what to measure: the integration patterns including smart commits, branch and pull request linking, deployment tracking and which system holds the truth, metrics such as DORA, cycle time and flow and what each measurement actually incentivises, and the anti-patterns that show up across both tools.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgithub-jira-deep-dive\u002Fskills\u002Fghjira-integration-metrics-and-anti-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ghjira-integration-metrics-and-anti-patterns\ndescription: \"Use when wiring GitHub and Jira together or deciding what to measure: the integration patterns including smart commits, branch and pull request linking, deployment tracking and which system holds the truth, metrics such as DORA, cycle time and flow and what each measurement actually incentivises, and the anti-patterns that show up across both tools.\"\n---\n\n# GitHub and Jira: Integrating GitHub and Jira, Metrics, and Anti-Patterns\n\n> **Part 5 of 6** of the *GitHub and Jira* reference (plugin `github-jira-deep-dive`), covering §23–§25. Sibling skills: `ghjira-git-data-model-branching-and-recovery` (§0–§4), `ghjira-github-repos-reviews-actions-security-and-identity` (§5–§12), `ghjira-jira-configuration-workflows-and-jql` (§13–§16), `ghjira-jira-boards-automation-permissions-and-hygiene` (§17–§22), `ghjira-reference` (§26–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Git's data model is fixed; the products churn constantly. See §26 → `ghjira-reference` for the two things that changed materially — Atlassian's Data Center wind-down, and GitHub's security and Copilot repackaging.\n\n> **⚠️ These are workflow systems, not just tools, and that's the whole framing.**\n> **Complements a Git-adjacent programming reference, a DevSecOps\u002FCI-CD reference\n> (pipeline design), and an engineering-process reference (the methodology these tools\n> encode).**\n>\n> **⚠️ GOTCHA** boxes mark configuration decisions that are painful or impossible to\n> reverse, and the places where the tool silently does something other than what you\n> expect.\n>\n> **⚠️ A currency warning specific to this file**: **product surfaces here change on a\n> scale of months.** ⚠️ **Treat §26 → `ghjira-reference`'s specifics as a snapshot with dates attached, verify\n> pricing and packaging against the vendor before making a decision, and expect the\n> mechanics in §1–§25 → `ghjira-git-data-model-branching-and-recovery`, `ghjira-github-repos-reviews-actions-security-and-identity`, `ghjira-jira-configuration-workflows-and-jql`, `ghjira-jira-boards-automation-permissions-and-hygiene` to outlive them.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ The tool does not fix the process** (§1 → `ghjira-git-data-model-branching-and-recovery`). **A broken workflow encoded in Jira is\n>    a broken workflow with better reporting, and most \"we need to configure X\" requests\n>    are really \"we haven't agreed how we work.\"**\n> 2. **⚠️ Understand Git's data model and most Git problems dissolve** (§2 → `ghjira-git-data-model-branching-and-recovery`). **Almost all\n>    Git confusion comes from learning commands instead of the object graph.**\n> 3. **⚠️ Configuration debt is the real cost in both systems** (§16 → `ghjira-jira-configuration-workflows-and-jql`, §24). **Every scheme,\n>    custom field, workflow and ruleset you add is permanent maintenance, and neither tool\n>    makes removal easy.**\n\n---\n\n## §23. Integrating GitHub and Jira\n\n**⚠️ The standard pattern is issue-key-in-branch-and-commit:**\n```\n⚠️ Branch name:   PROJ-123-short-description\n⚠️ Commit message: PROJ-123 fix the thing\n⚠️ PR title:      PROJ-123 Fix the thing\n   → ⚠️ Jira shows linked branches, commits, PRs and builds on the issue\n   → ⚠️ Smart commits can transition issues from the commit message\n   → ⚠️ Automation can transition on PR open\u002Fmerge (§19)\n```\n**⚠️ Why the convention matters more than the tooling**: ⚠️ **the entire integration hangs\non the issue key being present.** **Enforce it with a ruleset or a CI check rather than\nwith reminders.**\n**⚠️ The genuine architectural question**: ⚠️ **which system is the source of truth for\nSTATUS?** **Having both means reconciliation, and the workable answers are either\n\"Jira, and GitHub events update it automatically\" or \"engineers live in GitHub, Jira is\ngenerated.\"** **⚠️ What fails is asking people to update both manually.**\n**⚠️ Do you need both?** ⚠️ **For a single engineering team with no service-desk or\nportfolio needs, GitHub Issues and Projects may genuinely suffice** (§10 → `ghjira-github-repos-reviews-actions-security-and-identity`). **Jira earns its\nplace with multiple teams, non-engineering stakeholders, complex workflow requirements, or\nITSM** (§21 → `ghjira-jira-boards-automation-permissions-and-hygiene`).\n\n---\n\n## §24. ⚠️ Metrics\n\n**⚠️ DORA's four keys are the best-validated delivery metrics available:**\n```\n⚠️ DEPLOYMENT FREQUENCY · LEAD TIME FOR CHANGES  (throughput)\n⚠️ CHANGE FAILURE RATE · TIME TO RESTORE SERVICE (stability)\n⚠️ Later work adds RELIABILITY as a fifth\n```\n⚠️ **The key research finding is that throughput and stability are NOT a tradeoff** —\n**high performers do better on both, which refutes the \"move fast and break things vs move\nslow and be safe\" framing.**\n> **⚠️ GOTCHA — DORA metrics are TEAM diagnostics, not individual performance measures,\n> and using them for the latter destroys them.** ⚠️ **Anything measured in Jira or GitHub\n> can be gamed: commit counts reward churn, lines changed reward verbosity, story points\n> inflate, ticket counts reward splitting.** **⚠️ Goodhart's law is unusually fast here\n> because the measurement is fully under the measured party's control.**\n> **⚠️ Never measure individuals with these systems.** **Use them to find where WORK gets\n> stuck.**\n\n**⚠️ Flow metrics worth watching instead of output counts**: **cycle time distribution\n(⚠️ the 85th percentile is more useful than the mean for forecasting), WIP, flow\nefficiency (⚠️ active time ÷ total elapsed — typically shockingly low, often under 20%,\nand that gap IS the improvement opportunity), and blocked time.**\n**⚠️ The single most actionable thing in most teams is PR review latency** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) —\n**it's measurable, it's usually large, and it's fixable by agreement rather than tooling.**\n\n---\n\n## §25. Anti-Patterns\n\n```\n⚠️ Configuring the tool instead of deciding the process (§1)\n⚠️ Editing a shared Jira scheme without checking what else uses it (§13)\n⚠️ Creating a custom field instead of reusing one (§13, §22)\n⚠️ Choosing team-managed\u002Fcompany-managed without knowing the difference (§14)\n⚠️ Fifteen-status workflows nobody updates accurately (§15)\n⚠️ status != Done instead of resolution = Unresolved (§16)\n⚠️ Velocity as a cross-team or individual performance metric (§17, §24)\n⚠️ Huge pull requests, then complaining review is superficial (§6)\n⚠️ Long-lived feature branches, then blaming the merge tool (§3)\n⚠️ Rebasing shared history; force-push without --force-with-lease (§3)\n⚠️ pull_request_target with checkout of PR code (§8)\n⚠️ Unpinned third-party actions (§8)\n⚠️ Cleaning a leaked secret from history without rotating it first (§9)\n⚠️ PATs for automation instead of a GitHub App (§11)\n⚠️ Required status checks that never run on skipped paths (§7)\n⚠️ Dependabot version updates left ungrouped until everyone ignores them (§9)\n⚠️ Asking people to update both Jira and GitHub by hand (§23)\n⚠️ Measuring individuals with DORA metrics (§24)\n```\n","# GitHub and Jira: Integrating GitHub and Jira, Metrics, and Anti-Patterns\n\n> **Part 5 of 6** of the *GitHub and Jira* reference (plugin `github-jira-deep-dive`), covering §23–§25. Sibling skills: `ghjira-git-data-model-branching-and-recovery` (§0–§4), `ghjira-github-repos-reviews-actions-security-and-identity` (§5–§12), `ghjira-jira-configuration-workflows-and-jql` (§13–§16), `ghjira-jira-boards-automation-permissions-and-hygiene` (§17–§22), `ghjira-reference` (§26–§29). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Git's data model is fixed; the products churn constantly. See §26 → `ghjira-reference` for the two things that changed materially — Atlassian's Data Center wind-down, and GitHub's security and Copilot repackaging.\n\n> **⚠️ These are workflow systems, not just tools, and that's the whole framing.**\n> **Complements a Git-adjacent programming reference, a DevSecOps\u002FCI-CD reference\n> (pipeline design), and an engineering-process reference (the methodology these tools\n> encode).**\n>\n> **⚠️ GOTCHA** boxes mark configuration decisions that are painful or impossible to\n> reverse, and the places where the tool silently does something other than what you\n> expect.\n>\n> **⚠️ A currency warning specific to this file**: **product surfaces here change on a\n> scale of months.** ⚠️ **Treat §26 → `ghjira-reference`'s specifics as a snapshot with dates attached, verify\n> pricing and packaging against the vendor before making a decision, and expect the\n> mechanics in §1–§25 → `ghjira-git-data-model-branching-and-recovery`, `ghjira-github-repos-reviews-actions-security-and-identity`, `ghjira-jira-configuration-workflows-and-jql`, `ghjira-jira-boards-automation-permissions-and-hygiene` to outlive them.**\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ The tool does not fix the process** (§1 → `ghjira-git-data-model-branching-and-recovery`). **A broken workflow encoded in Jira is\n>    a broken workflow with better reporting, and most \"we need to configure X\" requests\n>    are really \"we haven't agreed how we work.\"**\n> 2. **⚠️ Understand Git's data model and most Git problems dissolve** (§2 → `ghjira-git-data-model-branching-and-recovery`). **Almost all\n>    Git confusion comes from learning commands instead of the object graph.**\n> 3. **⚠️ Configuration debt is the real cost in both systems** (§16 → `ghjira-jira-configuration-workflows-and-jql`, §24). **Every scheme,\n>    custom field, workflow and ruleset you add is permanent maintenance, and neither tool\n>    makes removal easy.**\n\n---\n\n## §23. Integrating GitHub and Jira\n\n**⚠️ The standard pattern is issue-key-in-branch-and-commit:**\n```\n⚠️ Branch name:   PROJ-123-short-description\n⚠️ Commit message: PROJ-123 fix the thing\n⚠️ PR title:      PROJ-123 Fix the thing\n   → ⚠️ Jira shows linked branches, commits, PRs and builds on the issue\n   → ⚠️ Smart commits can transition issues from the commit message\n   → ⚠️ Automation can transition on PR open\u002Fmerge (§19)\n```\n**⚠️ Why the convention matters more than the tooling**: ⚠️ **the entire integration hangs\non the issue key being present.** **Enforce it with a ruleset or a CI check rather than\nwith reminders.**\n**⚠️ The genuine architectural question**: ⚠️ **which system is the source of truth for\nSTATUS?** **Having both means reconciliation, and the workable answers are either\n\"Jira, and GitHub events update it automatically\" or \"engineers live in GitHub, Jira is\ngenerated.\"** **⚠️ What fails is asking people to update both manually.**\n**⚠️ Do you need both?** ⚠️ **For a single engineering team with no service-desk or\nportfolio needs, GitHub Issues and Projects may genuinely suffice** (§10 → `ghjira-github-repos-reviews-actions-security-and-identity`). **Jira earns its\nplace with multiple teams, non-engineering stakeholders, complex workflow requirements, or\nITSM** (§21 → `ghjira-jira-boards-automation-permissions-and-hygiene`).\n\n---\n\n## §24. ⚠️ Metrics\n\n**⚠️ DORA's four keys are the best-validated delivery metrics available:**\n```\n⚠️ DEPLOYMENT FREQUENCY · LEAD TIME FOR CHANGES  (throughput)\n⚠️ CHANGE FAILURE RATE · TIME TO RESTORE SERVICE (stability)\n⚠️ Later work adds RELIABILITY as a fifth\n```\n⚠️ **The key research finding is that throughput and stability are NOT a tradeoff** —\n**high performers do better on both, which refutes the \"move fast and break things vs move\nslow and be safe\" framing.**\n> **⚠️ GOTCHA — DORA metrics are TEAM diagnostics, not individual performance measures,\n> and using them for the latter destroys them.** ⚠️ **Anything measured in Jira or GitHub\n> can be gamed: commit counts reward churn, lines changed reward verbosity, story points\n> inflate, ticket counts reward splitting.** **⚠️ Goodhart's law is unusually fast here\n> because the measurement is fully under the measured party's control.**\n> **⚠️ Never measure individuals with these systems.** **Use them to find where WORK gets\n> stuck.**\n\n**⚠️ Flow metrics worth watching instead of output counts**: **cycle time distribution\n(⚠️ the 85th percentile is more useful than the mean for forecasting), WIP, flow\nefficiency (⚠️ active time ÷ total elapsed — typically shockingly low, often under 20%,\nand that gap IS the improvement opportunity), and blocked time.**\n**⚠️ The single most actionable thing in most teams is PR review latency** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) —\n**it's measurable, it's usually large, and it's fixable by agreement rather than tooling.**\n\n---\n\n## §25. Anti-Patterns\n\n```\n⚠️ Configuring the tool instead of deciding the process (§1)\n⚠️ Editing a shared Jira scheme without checking what else uses it (§13)\n⚠️ Creating a custom field instead of reusing one (§13, §22)\n⚠️ Choosing team-managed\u002Fcompany-managed without knowing the difference (§14)\n⚠️ Fifteen-status workflows nobody updates accurately (§15)\n⚠️ status != Done instead of resolution = Unresolved (§16)\n⚠️ Velocity as a cross-team or individual performance metric (§17, §24)\n⚠️ Huge pull requests, then complaining review is superficial (§6)\n⚠️ Long-lived feature branches, then blaming the merge tool (§3)\n⚠️ Rebasing shared history; force-push without --force-with-lease (§3)\n⚠️ pull_request_target with checkout of PR code (§8)\n⚠️ Unpinned third-party actions (§8)\n⚠️ Cleaning a leaked secret from history without rotating it first (§9)\n⚠️ PATs for automation instead of a GitHub App (§11)\n⚠️ Required status checks that never run on skipped paths (§7)\n⚠️ Dependabot version updates left ungrouped until everyone ignores them (§9)\n⚠️ Asking people to update both Jira and GitHub by hand (§23)\n⚠️ Measuring individuals with DORA metrics (§24)\n```\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgithub-jira-deep-dive\u002Fskills\u002Fghjira-integration-metrics-and-anti-patterns",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill ghjira-integration-metrics-and-anti-patterns",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill ghjira-integration-metrics-and-anti-patterns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill ghjira-integration-metrics-and-anti-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgithub-jira-deep-dive\u002Fskills\u002Fghjira-integration-metrics-and-anti-patterns\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]