[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP0AS9BET0V1HCW18TBCZM":3,"skill-same:01M7AP0AS9BET0V1HCW18TBCZM":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},"01M7AP0AS9BET0V1HCW18TBCZM","ghjira-reference",null,"Use when correcting a GitHub or Jira misconception, looking up a limit, quota or plan difference, or needing a command and JQL quick reference — plus the current state of Atlassian's Data Center wind-down and GitHub's security and Copilot repackaging. Companion to the other GitHub and Jira skills.","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-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ghjira-reference\ndescription: \"Use when correcting a GitHub or Jira misconception, looking up a limit, quota or plan difference, or needing a command and JQL quick reference — plus the current state of Atlassian's Data Center wind-down and GitHub's security and Copilot repackaging. Companion to the other GitHub and Jira skills.\"\n---\n\n# GitHub and Jira: What's Live, Misconceptions, and Quick Reference\n\n> **Part 6 of 6** of the *GitHub and Jira* reference (plugin `github-jira-deep-dive`), covering §26–§29. 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-integration-metrics-and-anti-patterns` (§23–§25). 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 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'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`, `ghjira-integration-metrics-and-anti-patterns` 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 → `ghjira-integration-metrics-and-anti-patterns`). **Every scheme,\n>    custom field, workflow and ruleset you add is permanent maintenance, and neither tool\n>    makes removal easy.**\n\n---\n\n## §26. What's Live — verified August 2026\n\n> **⚠️ Both vendors reprice and repackage frequently. Everything below carries a date;\n> verify against the vendor before committing budget.**\n\n### 26.1 ⚠️ Atlassian: Data Center is ending, and the dates are the whole story\n**⚠️ If you run self-managed Atlassian, this is a migration project with a deadline, not a\nwatching brief.**\n\n- **⚠️ Announced 8 September 2025.** **The timeline as published:**\n```\n⚠️ 17 Feb 2026   Data Center PRICE INCREASES take effect (~15% standard list;\n                 ⚠️ reported 18–40% for legacy \"Advantage\" pricing depending\n                 on tier, as those are brought to standard list)\n⚠️ 30 Mar 2026   END OF SALE for NEW customers. After this, Cloud is the only\n                 entry point to the Atlassian ecosystem\n⚠️ 30 Mar 2028   Last date EXISTING customers can buy new licences, app\n                 licences or tier expansions. After that: renewal only\n⚠️ 28 Mar 2029   END OF LIFE. Instances go READ-ONLY; no support, no updates\n```\n- **⚠️ Affected products include Jira Software, Jira Service Management, Confluence,\n  Bamboo and Crowd.** ⚠️ **Bitbucket Data Center is treated differently — reported dual\n  licensing for Bitbucket DC and Cloud, recognizing on-prem source-code requirements —\n  though sources characterize that as a reprieve rather than a permanent exemption.**\n- **⚠️ Feature development for Data Center has effectively stopped**; **innovation is in\n  Cloud only.**\n\n> **⚠️ GOTCHA — the \"existing customer\" definition is narrower than people assume and it\n> catches organizations off guard.** ⚠️ **Status is evaluated PER PRODUCT: if you run\n> Jira Software on Data Center today but want to add Jira Service Management on Data\n> Center, you are a NEW customer for that product and cannot.**\n> **⚠️ It's also evaluated per entity — a parent company's Data Center licences cannot be\n> extended to cover a newly acquired subsidiary after March 2026.** **⚠️ This matters\n> enormously for M&A and for phased platform expansion.**\n\n**⚠️ Constrained environments have a genuine problem, and it should be named**:\n⚠️ **air-gapped deployments have no Atlassian Cloud option; Atlassian's Isolated Cloud\n(expected 2026) is reported as internet-connected and Atlassian-managed.** ⚠️ **Government\nCloud has a much smaller app ecosystem — around 60 Marketplace apps versus 4,000+\ncommercially — with apps needing rebuilding as Forge apps.** **⚠️ And Jira Align has no\nreported compliant cloud path for some regulated users, which makes SAFe portfolio\nmanagement a separate tooling decision.**\n**⚠️ Rovo is the other commercial change to watch**: **Atlassian's AI layer, reported at\n$20\u002Fuser\u002Fmonth on Cloud Premium and Enterprise** — ⚠️ **the most expensive Atlassian\nadd-on, and appearing in enterprise renewal quotes.** **⚠️ Reported pricing model has\nshifted twice since launch; treat the number as a snapshot and evaluate genuine\nutilization before committing.**\n\n### 26.2 ⚠️ GitHub: security unbundled, Copilot repriced twice\n- **⚠️ GitHub Advanced Security no longer exists as a single SKU.** **From 1 April 2025 it\n  was split into two standalone products:**\n```\n⚠️ GITHUB SECRET PROTECTION  $19\u002Fmonth per ACTIVE COMMITTER\n   push protection, secret scanning, AI-powered detection\n⚠️ GITHUB CODE SECURITY      $30\u002Fmonth per active committer\n   code scanning, Copilot Autofix, security campaigns, Dependabot\n   features, dependency review, security overview\n```\n⚠️ **Crucially, GitHub Team plan customers can buy these without an Enterprise\nsubscription — which materially lowers the entry point for smaller orgs.**\n**⚠️ Note the billing unit: ACTIVE COMMITTER, not seat.** **That's a different and usually\nsmaller denominator than your licence count, and it makes cost modelling non-obvious.**\n- **⚠️ Free assessment tooling arrived**: **a Secret Risk Assessment and, more recently, a\n  Code Security Risk Assessment giving a free one-click CodeQL scan of up to 20 active\n  repositories with no licence required and no Actions minutes consumed.** ⚠️ **That's a\n  genuinely useful way to size your exposure before buying anything.**\n\n> **⚠️ GOTCHA — Copilot's billing model changed fundamentally, and the reason is\n> instructive.** ⚠️ **All Copilot plans moved to usage-based AI CREDIT billing on 1 June\n> 2026 (reported at $0.01 per credit), with costs tracking actual model usage rather than\n> a fixed request count.**\n> **⚠️ The driver was agentic workloads: GitHub paused new sign-ups for Pro, Pro+ and\n> Student plans in a reported 58-day freeze beginning 20 April 2026**, ⚠️ **with GitHub's\n> VP of Product attributing it to long-running parallelized agentic sessions consuming far\n> more resources than flat-rate plans could support.**\n> **⚠️ Sign-ups reopened gradually from 17 June 2026, per GitHub's own changelog, and a\n> new $100\u002Fmonth Max plan was added** alongside Free, Pro and Pro+ — **$200 in monthly AI\n> credits and roughly 2.9× Pro+'s usage headroom.**\n> **⚠️ The generalizable lesson: flat-rate pricing does not survive agentic usage\n> patterns, and anyone budgeting for AI coding tools on a per-seat assumption should\n> expect that assumption to break.**\n\n- **⚠️ Agentic features moved from autocomplete to delegated work.** **Copilot coding agent\n  can be assigned a GitHub Issue, works asynchronously in an ephemeral Actions-powered\n  environment on a branch, and opens a PR for human review.** ⚠️ **Agentic code review\n  shipped around March 2026.** **⚠️ The human-review-before-merge gate is the important\n  design point, and your rulesets (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) are what enforce it.**\n- **⚠️ Rulesets continue to displace classic branch protection** — **automatic conversion\n  of branch protection rules into rulesets is now available, along with a rule insights\n  dashboard showing blocked-push trends over time.**\n- **⚠️ Actions**: **custom runner autoscaling, expanded security controls, and reported\n  hosted-runner price reductions of up to 39% in January 2026.** ⚠️ **Also note read-only\n  cache tokens for workflows triggerable without write permissions — a supply-chain\n  hardening change.**\n\n---\n\n## §27. Misconceptions\n\n| Misconception | Correction |\n|---|---|\n| Git commits store diffs | ⚠️ **They store snapshots; diffs are computed** (§2 → `ghjira-git-data-model-branching-and-recovery`) |\n| A branch contains commits | ⚠️ **It's a pointer. Deleting it loses nothing** (§2 → `ghjira-git-data-model-branching-and-recovery`, §4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Deleting a branch loses the work | ⚠️ **Reflog. Committed work is hard to lose** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Rebase is just a tidier merge | ⚠️ **It rewrites hashes. Never on shared history** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| `git revert` undoes like `reset` | ⚠️ **Revert makes a NEW commit — correct on shared branches** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Git Flow is the professional standard | ⚠️ **Built for versioned releases; overkill for web apps** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| Bigger PRs are more efficient to review | ⚠️ **Defect detection drops sharply with size** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| A GitHub team can deny access | ⚠️ **Permissions are additive; there is no deny** (§5 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Required checks always block | ⚠️ **A skipped workflow never reports — PR hangs** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| `pull_request_target` is a safer trigger | ⚠️ **It's a secrets-exfiltration footgun** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Pinning an action to a tag is fine | ⚠️ **Tags are mutable. Pin the SHA** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Scrub the leaked secret from history | ⚠️ **ROTATE first. Removal doesn't undo exposure** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Use a PAT for the automation | ⚠️ **Use a GitHub App** (§11 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| GHAS is one product | ⚠️ **Split into Secret Protection and Code Security** (§26.2) |\n| Copilot is flat-rate per seat | ⚠️ **Usage-based AI credits since June 2026** (§26.2) |\n| Editing a Jira workflow affects one project | ⚠️ **Schemes are shared. Check first** (§13 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Team-managed vs company-managed is cosmetic | ⚠️ **No clean conversion path** (§14 → `ghjira-jira-configuration-workflows-and-jql`) |\n| `status != Done` finds open issues | ⚠️ **Misses other terminal statuses. Use resolution** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Story points are hours | ⚠️ **Relative size; converted empirically by throughput** (§17 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Velocity compares teams | ⚠️ **It doesn't, and using it that way inflates points** (§17 → `ghjira-jira-boards-automation-permissions-and-hygiene`, §24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Burndown shows what happened | ⚠️ **Burnup shows scope change; burndown hides it** (§18 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| More statuses means better tracking | ⚠️ **More places to be inaccurate** (§15 → `ghjira-jira-configuration-workflows-and-jql`) |\n| DORA metrics measure developers | ⚠️ **Team diagnostics. Individual use destroys them** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Speed and stability trade off | ⚠️ **DORA finds high performers do better on both** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Data Center is fine until 2029 | ⚠️ **New-customer sale ended March 2026; expansions end 2028** (§26.1) |\n| We're an existing DC customer, so we're covered | ⚠️ **Evaluated per product and per entity** (§26.1) |\n\n---\n\n## §28. Quick Reference\n\n### 28.1 Picker\n| Question | Where |\n|---|---|\n| I broke my repo | ⚠️ **`git reflog` first, always** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Merge or rebase? | ⚠️ **Rebase your unpushed work; merge shared branches** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| Undo a commit others have pulled | ⚠️ **`git revert`, not reset** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Reviews are superficial | ⚠️ **The PRs are too big** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| PR stuck on a check that never runs | ⚠️ **Path filter + required check** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Automating against GitHub | ⚠️ **GitHub App, not a PAT** (§11 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Secret got committed | ⚠️ **ROTATE it, then clean history** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Enforcing policy across many repos | ⚠️ **Org-level rulesets** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| New Jira project — which type? | ⚠️ **§14 → `ghjira-jira-configuration-workflows-and-jql`, and decide deliberately** |\n| Need a new Jira field | ⚠️ **Check whether one exists first** (§13 → `ghjira-jira-configuration-workflows-and-jql`, §22 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Editing a Jira workflow | ⚠️ **Check what else uses the scheme** (§13 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Find my open work | ⚠️ **`assignee = currentUser() AND resolution = Unresolved`** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| What's been stuck? | ⚠️ **`status WAS \"Blocked\" DURING (-30d, now())`** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| People forget to update tickets | ⚠️ **Automation, not reminders** (§19 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Which is source of truth for status? | ⚠️ **Pick one; automate the other** (§23 → `ghjira-integration-metrics-and-anti-patterns`) |\n| What should we measure? | ⚠️ **DORA + cycle time. Never individuals** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Self-managed Atlassian, what now? | ⚠️ **§26.1's dates. This is a project** |\n\n### 28.2 Setup checklist for a new repo\n- [ ] ⚠️ **Ruleset on the default branch: PR required, checks required, no force push** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] CODEOWNERS, and owner review required rather than requested (§5 → `ghjira-github-repos-reviews-actions-security-and-identity`, §7 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **One merge strategy chosen and enforced** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **`permissions:` set explicitly in workflows; actions pinned to SHA** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **Secret scanning with PUSH PROTECTION enabled** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] Dependabot on, version updates grouped (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **OIDC to cloud providers rather than stored credentials** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] Concurrency groups to cancel superseded runs (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **Issue key convention enforced by check, not by reminder** (§23 → `ghjira-integration-metrics-and-anti-patterns`)\n\n---\n\n## §29. Method\n\n**§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`, `ghjira-integration-metrics-and-anti-patterns` rests on stable mechanics** — **Git's object model, the permission and scheme\narchitectures, JQL semantics, review and flow research, and the DORA findings.**\n⚠️ **The Git internals in §2 → `ghjira-git-data-model-branching-and-recovery` have been unchanged since 2005 and are the most durable\ncontent here.**\n\n**Two searches were run in August 2026**, on **Atlassian's Data Center wind-down** and\n**GitHub's security and Copilot repackaging** — ⚠️ **the two changes with real budget and\nmigration consequences.**\n\n**Confidence.** **High** in §2 → `ghjira-git-data-model-branching-and-recovery`, §13 → `ghjira-jira-configuration-workflows-and-jql` and §14 → `ghjira-jira-configuration-workflows-and-jql`, which are the sections I'd most want read.\n⚠️ **The \"commits are snapshots, branches are pointers\" framing dissolves most Git\nconfusion**, **and §13 → `ghjira-jira-configuration-workflows-and-jql`'s shared-scheme gotcha plus §14 → `ghjira-jira-configuration-workflows-and-jql`'s irreversible project-type choice\nare the two ways people most commonly damage a Jira instance without realizing it at the\ntime.**\n\n**High** in §26.1's timeline, which comes from Atlassian's own licensing pages and is\ncorroborated across multiple partner and analyst sources: ⚠️ **price increases 17 February\n2026, end of sale to new customers 30 March 2026, end of expansions 30 March 2028, end of\nlife 28 March 2029.** ⚠️ **The per-product and per-entity \"existing customer\" definition is\nthe detail I'd most want flagged** — **it's specific, it's counterintuitive, and it catches\norganizations mid-expansion or mid-acquisition.** **The percentage increases (~15% standard,\n18–40% legacy Advantage) come from partner and reseller commentary rather than\nAtlassian's own pricing page, so treat those as reported.**\n\n**High** in §26.2's GHAS split and pricing, which trace to GitHub's own changelog and\nresources pages. ⚠️ **The Copilot AI-credits transition (1 June 2026) and the reported\n58-day sign-up freeze from 20 April 2026 come from secondary tech coverage rather than\nGitHub's own announcements in my results** — **I've attributed them as reported.**\n⚠️ **The generalizable point is mine and I think it's the useful takeaway: flat-rate\npricing does not survive agentic usage, so per-seat budget assumptions for AI coding tools\nshould be expected to break.**\n\n⚠️ **Sourcing caution specific to this file**: **much of the Atlassian material comes from\nmigration consultancies and competing vendors, who have an obvious interest in urgency\naround Data Center EOL.** **I anchored the dates on Atlassian's own pages and used the\npartner sources only for the price-increase percentages and the practical implications,\nflagging those as reported.** ⚠️ **Similarly, several GitHub pricing figures come from\nthird-party pricing-guide sites; the product names, split, and per-active-committer\nbilling unit are confirmed by GitHub's own changelog.**\n","# GitHub and Jira: What's Live, Misconceptions, and Quick Reference\n\n> **Part 6 of 6** of the *GitHub and Jira* reference (plugin `github-jira-deep-dive`), covering §26–§29. 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-integration-metrics-and-anti-patterns` (§23–§25). 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 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'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`, `ghjira-integration-metrics-and-anti-patterns` 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 → `ghjira-integration-metrics-and-anti-patterns`). **Every scheme,\n>    custom field, workflow and ruleset you add is permanent maintenance, and neither tool\n>    makes removal easy.**\n\n---\n\n## §26. What's Live — verified August 2026\n\n> **⚠️ Both vendors reprice and repackage frequently. Everything below carries a date;\n> verify against the vendor before committing budget.**\n\n### 26.1 ⚠️ Atlassian: Data Center is ending, and the dates are the whole story\n**⚠️ If you run self-managed Atlassian, this is a migration project with a deadline, not a\nwatching brief.**\n\n- **⚠️ Announced 8 September 2025.** **The timeline as published:**\n```\n⚠️ 17 Feb 2026   Data Center PRICE INCREASES take effect (~15% standard list;\n                 ⚠️ reported 18–40% for legacy \"Advantage\" pricing depending\n                 on tier, as those are brought to standard list)\n⚠️ 30 Mar 2026   END OF SALE for NEW customers. After this, Cloud is the only\n                 entry point to the Atlassian ecosystem\n⚠️ 30 Mar 2028   Last date EXISTING customers can buy new licences, app\n                 licences or tier expansions. After that: renewal only\n⚠️ 28 Mar 2029   END OF LIFE. Instances go READ-ONLY; no support, no updates\n```\n- **⚠️ Affected products include Jira Software, Jira Service Management, Confluence,\n  Bamboo and Crowd.** ⚠️ **Bitbucket Data Center is treated differently — reported dual\n  licensing for Bitbucket DC and Cloud, recognizing on-prem source-code requirements —\n  though sources characterize that as a reprieve rather than a permanent exemption.**\n- **⚠️ Feature development for Data Center has effectively stopped**; **innovation is in\n  Cloud only.**\n\n> **⚠️ GOTCHA — the \"existing customer\" definition is narrower than people assume and it\n> catches organizations off guard.** ⚠️ **Status is evaluated PER PRODUCT: if you run\n> Jira Software on Data Center today but want to add Jira Service Management on Data\n> Center, you are a NEW customer for that product and cannot.**\n> **⚠️ It's also evaluated per entity — a parent company's Data Center licences cannot be\n> extended to cover a newly acquired subsidiary after March 2026.** **⚠️ This matters\n> enormously for M&A and for phased platform expansion.**\n\n**⚠️ Constrained environments have a genuine problem, and it should be named**:\n⚠️ **air-gapped deployments have no Atlassian Cloud option; Atlassian's Isolated Cloud\n(expected 2026) is reported as internet-connected and Atlassian-managed.** ⚠️ **Government\nCloud has a much smaller app ecosystem — around 60 Marketplace apps versus 4,000+\ncommercially — with apps needing rebuilding as Forge apps.** **⚠️ And Jira Align has no\nreported compliant cloud path for some regulated users, which makes SAFe portfolio\nmanagement a separate tooling decision.**\n**⚠️ Rovo is the other commercial change to watch**: **Atlassian's AI layer, reported at\n$20\u002Fuser\u002Fmonth on Cloud Premium and Enterprise** — ⚠️ **the most expensive Atlassian\nadd-on, and appearing in enterprise renewal quotes.** **⚠️ Reported pricing model has\nshifted twice since launch; treat the number as a snapshot and evaluate genuine\nutilization before committing.**\n\n### 26.2 ⚠️ GitHub: security unbundled, Copilot repriced twice\n- **⚠️ GitHub Advanced Security no longer exists as a single SKU.** **From 1 April 2025 it\n  was split into two standalone products:**\n```\n⚠️ GITHUB SECRET PROTECTION  $19\u002Fmonth per ACTIVE COMMITTER\n   push protection, secret scanning, AI-powered detection\n⚠️ GITHUB CODE SECURITY      $30\u002Fmonth per active committer\n   code scanning, Copilot Autofix, security campaigns, Dependabot\n   features, dependency review, security overview\n```\n⚠️ **Crucially, GitHub Team plan customers can buy these without an Enterprise\nsubscription — which materially lowers the entry point for smaller orgs.**\n**⚠️ Note the billing unit: ACTIVE COMMITTER, not seat.** **That's a different and usually\nsmaller denominator than your licence count, and it makes cost modelling non-obvious.**\n- **⚠️ Free assessment tooling arrived**: **a Secret Risk Assessment and, more recently, a\n  Code Security Risk Assessment giving a free one-click CodeQL scan of up to 20 active\n  repositories with no licence required and no Actions minutes consumed.** ⚠️ **That's a\n  genuinely useful way to size your exposure before buying anything.**\n\n> **⚠️ GOTCHA — Copilot's billing model changed fundamentally, and the reason is\n> instructive.** ⚠️ **All Copilot plans moved to usage-based AI CREDIT billing on 1 June\n> 2026 (reported at $0.01 per credit), with costs tracking actual model usage rather than\n> a fixed request count.**\n> **⚠️ The driver was agentic workloads: GitHub paused new sign-ups for Pro, Pro+ and\n> Student plans in a reported 58-day freeze beginning 20 April 2026**, ⚠️ **with GitHub's\n> VP of Product attributing it to long-running parallelized agentic sessions consuming far\n> more resources than flat-rate plans could support.**\n> **⚠️ Sign-ups reopened gradually from 17 June 2026, per GitHub's own changelog, and a\n> new $100\u002Fmonth Max plan was added** alongside Free, Pro and Pro+ — **$200 in monthly AI\n> credits and roughly 2.9× Pro+'s usage headroom.**\n> **⚠️ The generalizable lesson: flat-rate pricing does not survive agentic usage\n> patterns, and anyone budgeting for AI coding tools on a per-seat assumption should\n> expect that assumption to break.**\n\n- **⚠️ Agentic features moved from autocomplete to delegated work.** **Copilot coding agent\n  can be assigned a GitHub Issue, works asynchronously in an ephemeral Actions-powered\n  environment on a branch, and opens a PR for human review.** ⚠️ **Agentic code review\n  shipped around March 2026.** **⚠️ The human-review-before-merge gate is the important\n  design point, and your rulesets (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) are what enforce it.**\n- **⚠️ Rulesets continue to displace classic branch protection** — **automatic conversion\n  of branch protection rules into rulesets is now available, along with a rule insights\n  dashboard showing blocked-push trends over time.**\n- **⚠️ Actions**: **custom runner autoscaling, expanded security controls, and reported\n  hosted-runner price reductions of up to 39% in January 2026.** ⚠️ **Also note read-only\n  cache tokens for workflows triggerable without write permissions — a supply-chain\n  hardening change.**\n\n---\n\n## §27. Misconceptions\n\n| Misconception | Correction |\n|---|---|\n| Git commits store diffs | ⚠️ **They store snapshots; diffs are computed** (§2 → `ghjira-git-data-model-branching-and-recovery`) |\n| A branch contains commits | ⚠️ **It's a pointer. Deleting it loses nothing** (§2 → `ghjira-git-data-model-branching-and-recovery`, §4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Deleting a branch loses the work | ⚠️ **Reflog. Committed work is hard to lose** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Rebase is just a tidier merge | ⚠️ **It rewrites hashes. Never on shared history** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| `git revert` undoes like `reset` | ⚠️ **Revert makes a NEW commit — correct on shared branches** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Git Flow is the professional standard | ⚠️ **Built for versioned releases; overkill for web apps** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| Bigger PRs are more efficient to review | ⚠️ **Defect detection drops sharply with size** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| A GitHub team can deny access | ⚠️ **Permissions are additive; there is no deny** (§5 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Required checks always block | ⚠️ **A skipped workflow never reports — PR hangs** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| `pull_request_target` is a safer trigger | ⚠️ **It's a secrets-exfiltration footgun** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Pinning an action to a tag is fine | ⚠️ **Tags are mutable. Pin the SHA** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Scrub the leaked secret from history | ⚠️ **ROTATE first. Removal doesn't undo exposure** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Use a PAT for the automation | ⚠️ **Use a GitHub App** (§11 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| GHAS is one product | ⚠️ **Split into Secret Protection and Code Security** (§26.2) |\n| Copilot is flat-rate per seat | ⚠️ **Usage-based AI credits since June 2026** (§26.2) |\n| Editing a Jira workflow affects one project | ⚠️ **Schemes are shared. Check first** (§13 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Team-managed vs company-managed is cosmetic | ⚠️ **No clean conversion path** (§14 → `ghjira-jira-configuration-workflows-and-jql`) |\n| `status != Done` finds open issues | ⚠️ **Misses other terminal statuses. Use resolution** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Story points are hours | ⚠️ **Relative size; converted empirically by throughput** (§17 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Velocity compares teams | ⚠️ **It doesn't, and using it that way inflates points** (§17 → `ghjira-jira-boards-automation-permissions-and-hygiene`, §24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Burndown shows what happened | ⚠️ **Burnup shows scope change; burndown hides it** (§18 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| More statuses means better tracking | ⚠️ **More places to be inaccurate** (§15 → `ghjira-jira-configuration-workflows-and-jql`) |\n| DORA metrics measure developers | ⚠️ **Team diagnostics. Individual use destroys them** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Speed and stability trade off | ⚠️ **DORA finds high performers do better on both** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Data Center is fine until 2029 | ⚠️ **New-customer sale ended March 2026; expansions end 2028** (§26.1) |\n| We're an existing DC customer, so we're covered | ⚠️ **Evaluated per product and per entity** (§26.1) |\n\n---\n\n## §28. Quick Reference\n\n### 28.1 Picker\n| Question | Where |\n|---|---|\n| I broke my repo | ⚠️ **`git reflog` first, always** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Merge or rebase? | ⚠️ **Rebase your unpushed work; merge shared branches** (§3 → `ghjira-git-data-model-branching-and-recovery`) |\n| Undo a commit others have pulled | ⚠️ **`git revert`, not reset** (§4 → `ghjira-git-data-model-branching-and-recovery`) |\n| Reviews are superficial | ⚠️ **The PRs are too big** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| PR stuck on a check that never runs | ⚠️ **Path filter + required check** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Automating against GitHub | ⚠️ **GitHub App, not a PAT** (§11 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Secret got committed | ⚠️ **ROTATE it, then clean history** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| Enforcing policy across many repos | ⚠️ **Org-level rulesets** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`) |\n| New Jira project — which type? | ⚠️ **§14 → `ghjira-jira-configuration-workflows-and-jql`, and decide deliberately** |\n| Need a new Jira field | ⚠️ **Check whether one exists first** (§13 → `ghjira-jira-configuration-workflows-and-jql`, §22 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Editing a Jira workflow | ⚠️ **Check what else uses the scheme** (§13 → `ghjira-jira-configuration-workflows-and-jql`) |\n| Find my open work | ⚠️ **`assignee = currentUser() AND resolution = Unresolved`** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| What's been stuck? | ⚠️ **`status WAS \"Blocked\" DURING (-30d, now())`** (§16 → `ghjira-jira-configuration-workflows-and-jql`) |\n| People forget to update tickets | ⚠️ **Automation, not reminders** (§19 → `ghjira-jira-boards-automation-permissions-and-hygiene`) |\n| Which is source of truth for status? | ⚠️ **Pick one; automate the other** (§23 → `ghjira-integration-metrics-and-anti-patterns`) |\n| What should we measure? | ⚠️ **DORA + cycle time. Never individuals** (§24 → `ghjira-integration-metrics-and-anti-patterns`) |\n| Self-managed Atlassian, what now? | ⚠️ **§26.1's dates. This is a project** |\n\n### 28.2 Setup checklist for a new repo\n- [ ] ⚠️ **Ruleset on the default branch: PR required, checks required, no force push** (§7 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] CODEOWNERS, and owner review required rather than requested (§5 → `ghjira-github-repos-reviews-actions-security-and-identity`, §7 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **One merge strategy chosen and enforced** (§6 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **`permissions:` set explicitly in workflows; actions pinned to SHA** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **Secret scanning with PUSH PROTECTION enabled** (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] Dependabot on, version updates grouped (§9 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **OIDC to cloud providers rather than stored credentials** (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] Concurrency groups to cancel superseded runs (§8 → `ghjira-github-repos-reviews-actions-security-and-identity`)\n- [ ] ⚠️ **Issue key convention enforced by check, not by reminder** (§23 → `ghjira-integration-metrics-and-anti-patterns`)\n\n---\n\n## §29. Method\n\n**§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`, `ghjira-integration-metrics-and-anti-patterns` rests on stable mechanics** — **Git's object model, the permission and scheme\narchitectures, JQL semantics, review and flow research, and the DORA findings.**\n⚠️ **The Git internals in §2 → `ghjira-git-data-model-branching-and-recovery` have been unchanged since 2005 and are the most durable\ncontent here.**\n\n**Two searches were run in August 2026**, on **Atlassian's Data Center wind-down** and\n**GitHub's security and Copilot repackaging** — ⚠️ **the two changes with real budget and\nmigration consequences.**\n\n**Confidence.** **High** in §2 → `ghjira-git-data-model-branching-and-recovery`, §13 → `ghjira-jira-configuration-workflows-and-jql` and §14 → `ghjira-jira-configuration-workflows-and-jql`, which are the sections I'd most want read.\n⚠️ **The \"commits are snapshots, branches are pointers\" framing dissolves most Git\nconfusion**, **and §13 → `ghjira-jira-configuration-workflows-and-jql`'s shared-scheme gotcha plus §14 → `ghjira-jira-configuration-workflows-and-jql`'s irreversible project-type choice\nare the two ways people most commonly damage a Jira instance without realizing it at the\ntime.**\n\n**High** in §26.1's timeline, which comes from Atlassian's own licensing pages and is\ncorroborated across multiple partner and analyst sources: ⚠️ **price increases 17 February\n2026, end of sale to new customers 30 March 2026, end of expansions 30 March 2028, end of\nlife 28 March 2029.** ⚠️ **The per-product and per-entity \"existing customer\" definition is\nthe detail I'd most want flagged** — **it's specific, it's counterintuitive, and it catches\norganizations mid-expansion or mid-acquisition.** **The percentage increases (~15% standard,\n18–40% legacy Advantage) come from partner and reseller commentary rather than\nAtlassian's own pricing page, so treat those as reported.**\n\n**High** in §26.2's GHAS split and pricing, which trace to GitHub's own changelog and\nresources pages. ⚠️ **The Copilot AI-credits transition (1 June 2026) and the reported\n58-day sign-up freeze from 20 April 2026 come from secondary tech coverage rather than\nGitHub's own announcements in my results** — **I've attributed them as reported.**\n⚠️ **The generalizable point is mine and I think it's the useful takeaway: flat-rate\npricing does not survive agentic usage, so per-seat budget assumptions for AI coding tools\nshould be expected to break.**\n\n⚠️ **Sourcing caution specific to this file**: **much of the Atlassian material comes from\nmigration consultancies and competing vendors, who have an obvious interest in urgency\naround Data Center EOL.** **I anchored the dates on Atlassian's own pages and used the\npartner sources only for the price-increase percentages and the practical implications,\nflagging those as reported.** ⚠️ **Similarly, several GitHub pricing figures come from\nthird-party pricing-guide sites; the product names, split, and per-active-committer\nbilling unit are confirmed by GitHub's own changelog.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgithub-jira-deep-dive\u002Fskills\u002Fghjira-reference",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-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill ghjira-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill ghjira-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fgithub-jira-deep-dive\u002Fskills\u002Fghjira-reference\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",[],[]]