[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMY2JC5VN6FKWR67BQ2BJR":3,"skill-same:01M7AMY2JC5VN6FKWR67BQ2BJR":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},"01M7AMY2JC5VN6FKWR67BQ2BJR","github-atlassian",null,"Advanced practitioner reference for GitHub and the Atlassian suite (Jira, Confluence, JSM, Bitbucket) covering 2025–2026 changes: GitHub rulesets, merge queue, GHAS rebundling (Secret Protection $19\u002FCode Security $30), Copilot agent GA, AI Credits billing, artifact attestations, EMU; Atlassian Server EOL, Rovo bundling, JSM Service Collection, Forge replacing Connect, Data Center countdown; and the GitHub↔Jira integration pattern for 50–500 engineer orgs. Use when advising on GitHub governance, Atlassian configuration, tool selection, billing strategy, or cross-platform integration.","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\u002Fdevsecops-cicd\u002Fskills\u002Fgithub-atlassian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-atlassian\ndescription: \"Advanced practitioner reference for GitHub and the Atlassian suite (Jira, Confluence, JSM, Bitbucket) covering 2025–2026 changes: GitHub rulesets, merge queue, GHAS rebundling (Secret Protection $19\u002FCode Security $30), Copilot agent GA, AI Credits billing, artifact attestations, EMU; Atlassian Server EOL, Rovo bundling, JSM Service Collection, Forge replacing Connect, Data Center countdown; and the GitHub↔Jira integration pattern for 50–500 engineer orgs. Use when advising on GitHub governance, Atlassian configuration, tool selection, billing strategy, or cross-platform integration.\"\n---\n\n# GitHub & Atlassian: Advanced Practitioner Reference (2026)\n\n## The Three Things You Must Plan Around Now\n\n1. **GitHub billing changes (April–June 2026):** GHAS split into two SKUs (April 1, 2025); Copilot moved to usage-based AI Credits billing (June 1, 2026)\n2. **Bitbucket app-password hard deadline:** brownouts start June 9, 2026; permanent removal July 28, 2026\n3. **Atlassian Server is dead (Feb 2024); Data Center is on a countdown** — no new DC sales after March 30, 2026; full EOL March 28, 2029\n\n---\n\n## Part 1 — GitHub\n\n### 1.1 Repositories and Governance\n\n**Rulesets have superseded branch protection** as the model of choice:\n- Multiple rulesets **aggregate** (most restrictive applies) vs branch protection (one rule \"wins\" by priority)\n- Can be set at the **organization level** (GitHub Enterprise)\n- Target branch-name patterns and tags\n- Run in **evaluate (dry-run) mode** before enforcement\n- Enforce **metadata rules** (commit message, branch naming, author email) natively — eliminating pre-receive hooks\n- Branch protection still exists and layers with rulesets\n\n**Three repository visibilities:**\n- Public, private, and **internal** (enterprise accounts only) — internal = visible to all enterprise members, ideal for InnerSource\n\n**CODEOWNERS:** routes review by path (last matching pattern wins); can be required via rulesets.\n\n**GitHub merge queue (GA 2023):**\n- Builds speculative merge commits (base + PRs ahead + this PR) and merges FIFO once required checks pass\n- Requires the `merge_group` workflow trigger — **the single most common misconfiguration**\n- Does not support wildcard branch patterns\n- Designed and tested at scale (GitHub.com: 30,000+ PRs, 4.5M CI runs before GA)\n\n### 1.2 Issues and Projects\n\n**YAML issue forms** have largely superseded markdown templates for serious intake — structured dropdowns\u002Fcheckboxes\u002Fvalidations.\n\n**GitHub Issues vs Jira decision:**\n- GitHub Issues + Projects: free, markdown-native, zero context-switch — sufficient for teams under ~20–30 developers\n- Jira wins on: workflow enforcement (conditions\u002Fvalidators\u002Fpost-functions), velocity\u002Fburndown\u002FCFD reporting, cross-project portfolio visibility, issue hierarchy (Initiative→Epic→Story→Sub-task), 5,000+ Marketplace\n\n**GitHub Projects (v2) honest gaps vs Jira:**\n- No native velocity\u002Fcycle-time analytics\n- Flat hierarchy (no true epics\u002Fparent-child without task-list workarounds)\n- Limited fine-grained permissions (\"QA can only move to Done\" isn't expressible)\n- Managed via GraphQL API\n\n### 1.3 GitHub Actions\n\n**Core building blocks:** triggers, matrix builds, concurrency controls, reusable workflows (`workflow_call`) vs composite\u002FJS\u002FDocker actions.\n\n**Security and scale features:**\n- **OIDC federation:** bind to Environments (`environment:\u003Cenv>` subject) with required reviewers, not just branches — the right way to gate production\n- **Environments + deployment protection rules:** required reviewers, wait timers, branch restrictions\n- **Actions Runner Controller (ARC):** Kubernetes-native autoscaling using **ephemeral** runner pods (fresh pod per job, destroyed after — prevents state leakage and ensures no job is assigned to a shutting-down runner)\n  - ARC 0.14.0 (March 2026): moved to `actions\u002Fscaleset` library client\n  - Earlier releases added: native sidecar DinD, automatic pod retries (up to 5), OpenShift support, Azure Key Vault secret retrieval (GA), dual-stack IPv4\u002FIPv6\n\n**Security best practices:**\n- Pin third-party actions to commit SHAs (Dependabot updates them)\n- Minimize `GITHUB_TOKEN` permissions; set explicit `permissions` blocks\n- Marketplace actions introduce third-party supply-chain risk\n\n**Repository secrets\u002Fvariables scope:** org, repo, and environment levels.\n\n### 1.4 GitHub Advanced Security (GHAS) — Repriced April 1, 2025\n\nGHAS was unbundled into two metered, committer-priced SKUs available even on Team:\n\n| SKU | Price | Includes |\n|---|---|---|\n| **Secret Protection** | $19\u002Factive committer\u002Fmo | Push protection, validity checks, AI-detected generic secrets, 200+ partner patterns |\n| **Code Security** | $30\u002Factive committer\u002Fmo | CodeQL code scanning, Copilot Autofix, security campaigns, dependency review |\n\n**Active committer definition:** unique active committers on a 90-day window over repos where the feature is enabled.\n\n**Cost control:** scope to specific repos — org-wide enablement counts every contractor and bot that pushes.\n\n**Copilot Autofix:** covers 90%+ of alert types in JS\u002FTS\u002FJava\u002FPython; suggestions remediate 2\u002F3+ of found vulnerabilities.\n\n**Other security features:**\n- Dependabot: alerts, security updates, version updates, grouped updates via `dependabot.yml`\n- Secret scanning push protection: blocks at push; delegated bypass (approval workflow); validity checks against provider APIs\n- Custom patterns (up to 500\u002Forg via Hyperscan regex)\n- **Artifact attestations** (GA June 2024): `actions\u002Fattest-build-provenance` via Sigstore → SLSA Build Level 2 out of the box, Level 3 with reusable workflows; no key management; Kubernetes admission controller for enforcement\n- Security campaigns (2025): org-level security debt remediation workflows\n\n### 1.5 GitHub Copilot\n\n**The product is now a family of agents:**\n\n| Feature | Status | Notes |\n|---|---|---|\n| Code completions | GA | Unlimited and unbilled on paid plans |\n| Copilot Chat (IDE + GitHub.com) | GA | PR summaries, repo Q&A, slash commands, `@workspace` |\n| Copilot code review | GA (April 4, 2025) | Automatic (via rules) + on-demand; 1M+ devs in first month of preview |\n| Copilot coding agent | GA (Sept 25, 2025) | Assign issue → opens draft PR via GitHub Actions |\n| Copilot CLI | GA | — |\n| Agent mode (VS Code, JetBrains) | GA by early 2026 | Multi-file\u002Fmulti-step agentic sessions |\n\n**Billing changed June 1, 2026 to usage-based AI Credits (1 credit = $0.01, priced by token\u002Fmodel):**\n\n| Plan | Price | AI Credits included |\n|---|---|---|\n| Business | $19\u002Fuser\u002Fmo | $19 credits |\n| Enterprise | $39\u002Fuser\u002Fmo | $39 credits (also requires GHEC ~$21\u002Fuser → real cost ~$60\u002Fuser) |\n\n- Code completions remain unlimited and unbilled\n- **Copilot code review additionally consumes GitHub Actions minutes on private repos starting June 1, 2026** (public repos remain free)\n- Agentic sessions can consume credits and Actions minutes quickly — set spend alerts\n\n**Honest assessment:** measurably helps on boilerplate, tests, and low-to-medium-complexity well-tested codebases; underdelivers on novel architecture and large unfamiliar codebases.\n\n### 1.6 Enterprise Identity (EMU)\n\n**True SCIM provisioning requires GitHub Enterprise Cloud with Enterprise Managed Users (EMU).**\n- Standard GHEC: only SCIM-triggered invitations (not full provisioning)\n- **EMU hard tradeoff:** managed users cannot contribute to public repos or external OSS\n- Okta + Entra split-IdP combination is explicitly unsupported\n- **Data residency (GHE.com) requires EMU**\n\n**GitHub Enterprise options:**\n- **GHEC:** cloud-hosted, EMU optional, GitHub Connect bridge\n- **GHES:** self-hosted HA (primary-replica, backup-utils), GitHub Connect bridge to GHEC; air-gapped option\n\n### 1.7 Packages and Ecosystem\n\n**GHCR** for GitHub-native flows; choose **Azure Artifacts\u002FArtifactory** for polyglot enterprise artifact governance.\n\n**GitHub Apps vs OAuth Apps vs PATs vs Actions tokens:**\n- GitHub Apps (JWT→installation tokens): the right credential for automation\n- PATs: simpler but coarser; fine-grained PATs now available\n- Actions `GITHUB_TOKEN`: repo-scoped, short-lived — prefer over PATs in Actions workflows\n\n**Codespaces:** devcontainers + prebuilds; billed per compute-hour.\n\n---\n\n## Part 2 — Atlassian\n\n### 2.1 Server EOL and Data Center Countdown\n\n| Milestone | Date |\n|---|---|\n| Server end of support | February 15, 2024 — **DONE** |\n| No new DC sales | March 30, 2026 |\n| DC license\u002Ftier\u002Fapp purchases stop | March 30, 2028 |\n| DC full EOL (read-only) | March 28, 2029 |\n\nMigration path: Cloud Migration Assistant; \"Atlassian Ascend\"\u002FFastShift programs for 1,000+ user orgs.\nA Bitbucket Hybrid License (DC + Cloud) arrives mid-2026.\n\n### 2.2 Jira Software\n\n**Two project types:**\n- **Team-managed (formerly next-gen):** simple, autonomous\n- **Company-managed (classic):** deep scheme model (workflow, permission, notification, issue type, field, screen schemes + project roles) — required for workflow gates, cross-project portfolio\n\n**Hierarchy:** Initiatives (in Plans) → Epics → Stories\u002FTasks → Sub-tasks\n\n**Workflows:** statuses\u002Ftransitions with conditions, validators, post-functions — the feature that makes Jira worth it over GitHub Issues.\n\n**JQL tips:** write index-friendly queries; avoid full-text scans at scale; use functions (`currentUser()`, `membersOf()`, `startOfWeek()`).\n\n**Jira Automation:** no-code triggers\u002Fconditions\u002Factions\u002Fbranches at project and org level.\n\n**Jira Plans (Advanced Roadmaps):** cross-team\u002Fprogram planning and dependency tracking.\n\n### 2.3 Jira Service Management (JSM) — Now \"Service Collection\"\n\n**JSM + Assets + Rovo + Customer Service Management** are now sold as the Service Collection.\n\n**Premium tier (~$47–53\u002Fagent\u002Fmo) gates the features that matter:**\n- CMDB\u002FAssets\n- Change management with CI\u002FCD deployment gating\n- Major incident management\n- Atlassian Intelligence\n- Virtual Service Agent\n\n**Billed per agent** — requesters are free.\n\n**Opsgenie status:** new sales ended June 4, 2025; full shutdown April 5, 2027; capabilities folded into JSM.\n\n**JSM vs ServiceNow vs Zendesk:**\n- JSM wins: Atlassian-ecosystem integration, per-agent price\n- ServiceNow wins: heavyweight enterprise ITSM breadth\n- Zendesk wins: pure customer-facing support UX\n\n### 2.4 Rovo — Atlassian's AI Layer\n\n**\"Rovo for all\" (from April 9, 2025):** Rovo Search\u002FChat\u002FAgents\u002FStudio included in paid Jira\u002FConfluence\u002FJSM Cloud plans — no separate SKU for core features.\n\n**Credit allowances (pooled at org level, monthly, no rollover):**\n\n| Plan | Credits\u002Fuser\u002Fmo |\n|---|---|\n| Standard | 25 |\n| Premium | 70 |\n| Enterprise | 150 |\n\n- Jira, Confluence, and Service Collection\u002FJSM\n- A single Rovo Chat\u002FAgent question = 10 credits; Deep Research = 100 credits\n- Atlassian Intelligence (in-product drafting\u002Fsummaries) is the foundation; Rovo is the cross-product layer\n- **Rovo Dev** (for engineers — CLI, PR analysis) is a separate $20\u002Fdev\u002Fmo product with 2,000 credits\n- Rovo is **Cloud-only**\n- Rovo credit overages are not yet billed but Atlassian has signaled future consumption-based charging (≥90 days notice)\n\n### 2.5 Bitbucket — URGENT Deprecation\n\n**App-password hard deadline:**\n- No new creation: September 9, 2025 — **PASSED**\n- Controlled brownouts begin: June 9, 2026\n- Permanent removal: July 28, 2026\n\n**Action required immediately:** migrate all Bitbucket CI integrations to API tokens with scopes (or OIDC for cloud auth).\n\n**Bitbucket Pipelines OIDC:** `oidc: true` flag; `$BITBUCKET_STEP_OIDC_TOKEN` for keyless cloud auth.\n\n**Code Insights\u002FAnnotations API:** pushes CI quality\u002Fcoverage\u002Fsecurity results back onto PRs.\n\n**Bitbucket Pipelines vs GitHub Actions:**\n- Actions wins on: ecosystem (20,000+ marketplace), reusable workflows, matrix builds, macOS\u002FWindows runners, free minutes (2,000\u002Fmo vs Bitbucket's 50 free; Standard 2,500, Premium 3,500)\n- Pipelines wins on: simplicity and zero-config Jira deployment tracking\n\n**Main reason to keep Bitbucket:** native Jira integration — same-vendor, deeper integration than GitHub's, strongest reason Atlassian-centric orgs stay\n\n### 2.6 Confluence\n\n**Key capabilities:**\n- Spaces with a permission model (space admin; page view\u002Fadd\u002Fedit\u002Fdelete\u002Fexport)\n- Page hierarchy and restrictions\n- Fabric editor with macros (code, ToC, panels, status, live Jira issue lists, children display, excerpt\u002Fexcerpt-include)\n- **Whiteboards** (GA February 29, 2024): Cloud-only\n- **Databases** (broad rollout July 10, 2024): structured data as fields + entries, sync from Jira\u002FConfluence\u002FCSV — Cloud-only\n- CQL search and Confluence Analytics (Cloud)\n- Page properties + reports for lightweight tracking\n\n**Confluence vs Notion vs SharePoint:**\n- Confluence wins: Atlassian-integrated teams (live Jira embeds, JSM knowledge base, space permissions)\n- Notion wins: flexible databases\u002FUX for smaller teams\n- SharePoint wins: Microsoft 365-centric document governance\n\n### 2.7 Forge vs Connect\n\n**Forge has replaced Connect** as the app platform.\n\n| | Connect | Forge |\n|---|---|---|\n| Model | External iframe (third-party servers) | Serverless on Atlassian infrastructure |\n| Storage | External DB | Key-value + Forge SQL |\n| Compliance | Requires vendor trust | Preferred model (Atlassian-hosted) |\n| Status | **End of support Q4 2026** | Active, all new investment |\n\n**Connect deprecation timeline:**\n- No new Connect listings: September 17, 2025 — **PASSED**\n- No Connect updates: March 31, 2026\n- End of support: Q4 2026\n\n**Action required:** audit Connect app dependencies; confirm vendors have Forge versions before Q4 2026.\n\n### 2.8 Atlassian Guard (Security Layer)\n\n- **Guard Standard** (SSO\u002FSCIM\u002FAPI-token control\u002Faudit log) — included free in Cloud Enterprise\n- **Guard Premium** (data classification, content scanning\u002FDLP, anomalous-activity threat detection, extended audit) — currently supports Jira and Confluence\n\n---\n\n## Part 3 — GitHub ↔ Atlassian Integration\n\n### The Official \"GitHub for Jira\" App\n\n- Atlassian-maintained; **Jira Cloud only**\n- Links commits\u002Fbranches\u002FPRs\u002Fbuilds\u002Fdeployments to issues by string-matching the Jira issue key\n- Surfaces data in the Jira development panel, board card icons, Code\u002FReleases\u002FDeployments tabs, JQL\n- Smart commits: `PROJ-123 #comment ... #time 2h #done`\n- \"Create branch\" button in Jira; JQL queries over development data\n\n**Limitation:** only as reliable as naming discipline — which is why mature teams enforce issue-keyed branch names via rulesets and drive status transitions via Actions.\n\n**GitHub Enterprise Server ↔ Jira DC:** not supported by the native app — requires third-party (e.g., GitKraken's Git Integration for Jira).\n\n### Production Integration Pattern (50–500 Engineers)\n\n1. **Enforce issue-keyed branch names** via GitHub rulesets (regex rejecting non-conforming branches at push)\n2. **Drive Jira status transitions from GitHub Actions** on `pull_request`\u002F`push`\u002Fdeployment events calling the Jira API or `atlassian\u002Fgajira-*` actions — more reliable than smart commits (which depend on developer discipline and email matching)\n3. **Track deployments** via GitHub Environments → Jira deployment panel\n4. **Pipe CodeQL\u002FDependabot findings into Jira** as security issues via Actions for SLA-tracked remediation\n5. **Keep Jira as system of record;** use GitHub Projects only for engineering-local sprint views to avoid dual-maintenance\n\n---\n\n## Part 4 — Cross-Cutting Concerns\n\n### Org Design\n- Mono-repo vs poly-repo drives GitHub org\u002Fteam structure and Jira project layout (one project per team is the common default)\n- Standardize naming across both: branch names, PR titles, Jira summaries\n- Standardize identity: one IdP (Entra ID\u002FOkta) → GitHub teams via EMU SCIM → Jira groups\u002Froles via Guard SCIM\n\n### End-to-End Agile Delivery Flow\nJira issue → issue-keyed branch → PR (linked) → CI (Actions\u002FPipelines) → human + Copilot code review → merge queue → Jira transition → release → deployment tracked in Jira\n\n- **Dual-track agile:** Confluence (discovery) + Jira sprints (delivery)\n- **DoD enforcement:** Jira automation + GitHub required checks\n\n### DORA Metrics Cross-Platform\n- **Deployment frequency:** GitHub releases\u002Fdeployments\n- **Lead time:** Jira create → PR merge → deploy\n- **Change failure rate:** bug\u002Fincident tickets\n- **MTTR:** incident resolution\n- **Tooling:** LinearB, Sleuth, Faros AI, Jellyfish, Haystack\n\n### Security and Compliance Integration\n- GHAS findings → Jira security issues (via Actions)\n- Both audit logs → SIEM\n- JSM change requests linked to GitHub PRs\u002Fdeployments\n- Secret-scanning alerts → JSM incidents\n- Both platforms carry SOC 2 \u002F ISO 27001; Atlassian Cloud adds FedRAMP\n\n### Licensing and Cost Optimization\n| Product | Standard | Premium |\n|---|---|---|\n| Jira | ~$7.91\u002Fuser\u002Fmo | ~$14.54\u002Fuser\u002Fmo |\n| Confluence | ~$5.42\u002Fuser\u002Fmo | ~$10.44\u002Fuser\u002Fmo |\n| JSM | ~$20\u002Fagent\u002Fmo | ~$47–53\u002Fagent\u002Fmo |\n| GitHub Team | $4\u002Fuser\u002Fmo | — |\n| GitHub Enterprise | ~$21\u002Fuser\u002Fmo | — |\n| GHAS Secret Protection | $19\u002Fcommitter\u002Fmo | — |\n| GHAS Code Security | $30\u002Fcommitter\u002Fmo | — |\n| Copilot Business | $19\u002Fuser\u002Fmo | — |\n| Copilot Enterprise | $39\u002Fuser\u002Fmo (+ GHEC) | — |\n\n**Optimization levers:**\n- Prune inactive users (metered billing means unused seats still cost)\n- Scope GHAS to specific repos, not org-wide\n- Reconcile licenses against IdP group sync\n- Consolidate on Enterprise where volume discounts apply\n- Set Copilot spend alerts given usage-based billing\n\n---\n\n## Staged Implementation Roadmap\n\n### Stage 1 — Stabilize Identity and Deprecation Exposure (Now)\n1. **Migrate Bitbucket app passwords to API tokens\u002FOIDC before June 9, 2026 brownouts** — this is the most urgent hard deadline\n2. Audit Connect app dependencies; confirm vendors have Forge versions before Q4 2026\n3. Standardize SSO\u002FSCIM on one IdP feeding both ecosystems\n4. Decide **EMU vs standard GHEC** using the OSS-contribution and data-residency tests\n\n### Stage 2 — Modernize Governance (Next Quarter)\n1. Migrate branch protection → **organization rulesets** in evaluate mode first, then enforce; add metadata rules for issue-keyed branch names\n2. Enable **merge queue** on busy default branches (remember the `merge_group` trigger)\n3. Scope **GHAS Secret Protection + Code Security** to active repos; turn on push protection org-wide with delegated bypass\n\n### Stage 3 — Integrate and Measure (6–12 Months)\n1. Deploy GitHub for Jira; replace smart-commit reliance with Actions-driven transitions\n2. Stand up DORA metrics via a cross-platform tool\n3. Pilot **Copilot coding agent \u002F code review** and **Rovo agents** on contained workflows; set spend alerts\n\n### Thresholds That Change the Plan\n- Cross ~30 engineers or need workflow gates\u002Fportfolio reporting → move planning to Jira (not GitHub Projects)\n- Active-committer count balloons with bots\u002Fcontractors → re-scope GHAS repos to control cost\n- Copilot agentic usage drives credit overages → cap org spend and restrict premium models\n- Air-gapped\u002Fsovereign requirements → GHES + Bitbucket DC (until 2029)\n","# GitHub & Atlassian: Advanced Practitioner Reference (2026)\n\n## The Three Things You Must Plan Around Now\n\n1. **GitHub billing changes (April–June 2026):** GHAS split into two SKUs (April 1, 2025); Copilot moved to usage-based AI Credits billing (June 1, 2026)\n2. **Bitbucket app-password hard deadline:** brownouts start June 9, 2026; permanent removal July 28, 2026\n3. **Atlassian Server is dead (Feb 2024); Data Center is on a countdown** — no new DC sales after March 30, 2026; full EOL March 28, 2029\n\n---\n\n## Part 1 — GitHub\n\n### 1.1 Repositories and Governance\n\n**Rulesets have superseded branch protection** as the model of choice:\n- Multiple rulesets **aggregate** (most restrictive applies) vs branch protection (one rule \"wins\" by priority)\n- Can be set at the **organization level** (GitHub Enterprise)\n- Target branch-name patterns and tags\n- Run in **evaluate (dry-run) mode** before enforcement\n- Enforce **metadata rules** (commit message, branch naming, author email) natively — eliminating pre-receive hooks\n- Branch protection still exists and layers with rulesets\n\n**Three repository visibilities:**\n- Public, private, and **internal** (enterprise accounts only) — internal = visible to all enterprise members, ideal for InnerSource\n\n**CODEOWNERS:** routes review by path (last matching pattern wins); can be required via rulesets.\n\n**GitHub merge queue (GA 2023):**\n- Builds speculative merge commits (base + PRs ahead + this PR) and merges FIFO once required checks pass\n- Requires the `merge_group` workflow trigger — **the single most common misconfiguration**\n- Does not support wildcard branch patterns\n- Designed and tested at scale (GitHub.com: 30,000+ PRs, 4.5M CI runs before GA)\n\n### 1.2 Issues and Projects\n\n**YAML issue forms** have largely superseded markdown templates for serious intake — structured dropdowns\u002Fcheckboxes\u002Fvalidations.\n\n**GitHub Issues vs Jira decision:**\n- GitHub Issues + Projects: free, markdown-native, zero context-switch — sufficient for teams under ~20–30 developers\n- Jira wins on: workflow enforcement (conditions\u002Fvalidators\u002Fpost-functions), velocity\u002Fburndown\u002FCFD reporting, cross-project portfolio visibility, issue hierarchy (Initiative→Epic→Story→Sub-task), 5,000+ Marketplace\n\n**GitHub Projects (v2) honest gaps vs Jira:**\n- No native velocity\u002Fcycle-time analytics\n- Flat hierarchy (no true epics\u002Fparent-child without task-list workarounds)\n- Limited fine-grained permissions (\"QA can only move to Done\" isn't expressible)\n- Managed via GraphQL API\n\n### 1.3 GitHub Actions\n\n**Core building blocks:** triggers, matrix builds, concurrency controls, reusable workflows (`workflow_call`) vs composite\u002FJS\u002FDocker actions.\n\n**Security and scale features:**\n- **OIDC federation:** bind to Environments (`environment:\u003Cenv>` subject) with required reviewers, not just branches — the right way to gate production\n- **Environments + deployment protection rules:** required reviewers, wait timers, branch restrictions\n- **Actions Runner Controller (ARC):** Kubernetes-native autoscaling using **ephemeral** runner pods (fresh pod per job, destroyed after — prevents state leakage and ensures no job is assigned to a shutting-down runner)\n  - ARC 0.14.0 (March 2026): moved to `actions\u002Fscaleset` library client\n  - Earlier releases added: native sidecar DinD, automatic pod retries (up to 5), OpenShift support, Azure Key Vault secret retrieval (GA), dual-stack IPv4\u002FIPv6\n\n**Security best practices:**\n- Pin third-party actions to commit SHAs (Dependabot updates them)\n- Minimize `GITHUB_TOKEN` permissions; set explicit `permissions` blocks\n- Marketplace actions introduce third-party supply-chain risk\n\n**Repository secrets\u002Fvariables scope:** org, repo, and environment levels.\n\n### 1.4 GitHub Advanced Security (GHAS) — Repriced April 1, 2025\n\nGHAS was unbundled into two metered, committer-priced SKUs available even on Team:\n\n| SKU | Price | Includes |\n|---|---|---|\n| **Secret Protection** | $19\u002Factive committer\u002Fmo | Push protection, validity checks, AI-detected generic secrets, 200+ partner patterns |\n| **Code Security** | $30\u002Factive committer\u002Fmo | CodeQL code scanning, Copilot Autofix, security campaigns, dependency review |\n\n**Active committer definition:** unique active committers on a 90-day window over repos where the feature is enabled.\n\n**Cost control:** scope to specific repos — org-wide enablement counts every contractor and bot that pushes.\n\n**Copilot Autofix:** covers 90%+ of alert types in JS\u002FTS\u002FJava\u002FPython; suggestions remediate 2\u002F3+ of found vulnerabilities.\n\n**Other security features:**\n- Dependabot: alerts, security updates, version updates, grouped updates via `dependabot.yml`\n- Secret scanning push protection: blocks at push; delegated bypass (approval workflow); validity checks against provider APIs\n- Custom patterns (up to 500\u002Forg via Hyperscan regex)\n- **Artifact attestations** (GA June 2024): `actions\u002Fattest-build-provenance` via Sigstore → SLSA Build Level 2 out of the box, Level 3 with reusable workflows; no key management; Kubernetes admission controller for enforcement\n- Security campaigns (2025): org-level security debt remediation workflows\n\n### 1.5 GitHub Copilot\n\n**The product is now a family of agents:**\n\n| Feature | Status | Notes |\n|---|---|---|\n| Code completions | GA | Unlimited and unbilled on paid plans |\n| Copilot Chat (IDE + GitHub.com) | GA | PR summaries, repo Q&A, slash commands, `@workspace` |\n| Copilot code review | GA (April 4, 2025) | Automatic (via rules) + on-demand; 1M+ devs in first month of preview |\n| Copilot coding agent | GA (Sept 25, 2025) | Assign issue → opens draft PR via GitHub Actions |\n| Copilot CLI | GA | — |\n| Agent mode (VS Code, JetBrains) | GA by early 2026 | Multi-file\u002Fmulti-step agentic sessions |\n\n**Billing changed June 1, 2026 to usage-based AI Credits (1 credit = $0.01, priced by token\u002Fmodel):**\n\n| Plan | Price | AI Credits included |\n|---|---|---|\n| Business | $19\u002Fuser\u002Fmo | $19 credits |\n| Enterprise | $39\u002Fuser\u002Fmo | $39 credits (also requires GHEC ~$21\u002Fuser → real cost ~$60\u002Fuser) |\n\n- Code completions remain unlimited and unbilled\n- **Copilot code review additionally consumes GitHub Actions minutes on private repos starting June 1, 2026** (public repos remain free)\n- Agentic sessions can consume credits and Actions minutes quickly — set spend alerts\n\n**Honest assessment:** measurably helps on boilerplate, tests, and low-to-medium-complexity well-tested codebases; underdelivers on novel architecture and large unfamiliar codebases.\n\n### 1.6 Enterprise Identity (EMU)\n\n**True SCIM provisioning requires GitHub Enterprise Cloud with Enterprise Managed Users (EMU).**\n- Standard GHEC: only SCIM-triggered invitations (not full provisioning)\n- **EMU hard tradeoff:** managed users cannot contribute to public repos or external OSS\n- Okta + Entra split-IdP combination is explicitly unsupported\n- **Data residency (GHE.com) requires EMU**\n\n**GitHub Enterprise options:**\n- **GHEC:** cloud-hosted, EMU optional, GitHub Connect bridge\n- **GHES:** self-hosted HA (primary-replica, backup-utils), GitHub Connect bridge to GHEC; air-gapped option\n\n### 1.7 Packages and Ecosystem\n\n**GHCR** for GitHub-native flows; choose **Azure Artifacts\u002FArtifactory** for polyglot enterprise artifact governance.\n\n**GitHub Apps vs OAuth Apps vs PATs vs Actions tokens:**\n- GitHub Apps (JWT→installation tokens): the right credential for automation\n- PATs: simpler but coarser; fine-grained PATs now available\n- Actions `GITHUB_TOKEN`: repo-scoped, short-lived — prefer over PATs in Actions workflows\n\n**Codespaces:** devcontainers + prebuilds; billed per compute-hour.\n\n---\n\n## Part 2 — Atlassian\n\n### 2.1 Server EOL and Data Center Countdown\n\n| Milestone | Date |\n|---|---|\n| Server end of support | February 15, 2024 — **DONE** |\n| No new DC sales | March 30, 2026 |\n| DC license\u002Ftier\u002Fapp purchases stop | March 30, 2028 |\n| DC full EOL (read-only) | March 28, 2029 |\n\nMigration path: Cloud Migration Assistant; \"Atlassian Ascend\"\u002FFastShift programs for 1,000+ user orgs.\nA Bitbucket Hybrid License (DC + Cloud) arrives mid-2026.\n\n### 2.2 Jira Software\n\n**Two project types:**\n- **Team-managed (formerly next-gen):** simple, autonomous\n- **Company-managed (classic):** deep scheme model (workflow, permission, notification, issue type, field, screen schemes + project roles) — required for workflow gates, cross-project portfolio\n\n**Hierarchy:** Initiatives (in Plans) → Epics → Stories\u002FTasks → Sub-tasks\n\n**Workflows:** statuses\u002Ftransitions with conditions, validators, post-functions — the feature that makes Jira worth it over GitHub Issues.\n\n**JQL tips:** write index-friendly queries; avoid full-text scans at scale; use functions (`currentUser()`, `membersOf()`, `startOfWeek()`).\n\n**Jira Automation:** no-code triggers\u002Fconditions\u002Factions\u002Fbranches at project and org level.\n\n**Jira Plans (Advanced Roadmaps):** cross-team\u002Fprogram planning and dependency tracking.\n\n### 2.3 Jira Service Management (JSM) — Now \"Service Collection\"\n\n**JSM + Assets + Rovo + Customer Service Management** are now sold as the Service Collection.\n\n**Premium tier (~$47–53\u002Fagent\u002Fmo) gates the features that matter:**\n- CMDB\u002FAssets\n- Change management with CI\u002FCD deployment gating\n- Major incident management\n- Atlassian Intelligence\n- Virtual Service Agent\n\n**Billed per agent** — requesters are free.\n\n**Opsgenie status:** new sales ended June 4, 2025; full shutdown April 5, 2027; capabilities folded into JSM.\n\n**JSM vs ServiceNow vs Zendesk:**\n- JSM wins: Atlassian-ecosystem integration, per-agent price\n- ServiceNow wins: heavyweight enterprise ITSM breadth\n- Zendesk wins: pure customer-facing support UX\n\n### 2.4 Rovo — Atlassian's AI Layer\n\n**\"Rovo for all\" (from April 9, 2025):** Rovo Search\u002FChat\u002FAgents\u002FStudio included in paid Jira\u002FConfluence\u002FJSM Cloud plans — no separate SKU for core features.\n\n**Credit allowances (pooled at org level, monthly, no rollover):**\n\n| Plan | Credits\u002Fuser\u002Fmo |\n|---|---|\n| Standard | 25 |\n| Premium | 70 |\n| Enterprise | 150 |\n\n- Jira, Confluence, and Service Collection\u002FJSM\n- A single Rovo Chat\u002FAgent question = 10 credits; Deep Research = 100 credits\n- Atlassian Intelligence (in-product drafting\u002Fsummaries) is the foundation; Rovo is the cross-product layer\n- **Rovo Dev** (for engineers — CLI, PR analysis) is a separate $20\u002Fdev\u002Fmo product with 2,000 credits\n- Rovo is **Cloud-only**\n- Rovo credit overages are not yet billed but Atlassian has signaled future consumption-based charging (≥90 days notice)\n\n### 2.5 Bitbucket — URGENT Deprecation\n\n**App-password hard deadline:**\n- No new creation: September 9, 2025 — **PASSED**\n- Controlled brownouts begin: June 9, 2026\n- Permanent removal: July 28, 2026\n\n**Action required immediately:** migrate all Bitbucket CI integrations to API tokens with scopes (or OIDC for cloud auth).\n\n**Bitbucket Pipelines OIDC:** `oidc: true` flag; `$BITBUCKET_STEP_OIDC_TOKEN` for keyless cloud auth.\n\n**Code Insights\u002FAnnotations API:** pushes CI quality\u002Fcoverage\u002Fsecurity results back onto PRs.\n\n**Bitbucket Pipelines vs GitHub Actions:**\n- Actions wins on: ecosystem (20,000+ marketplace), reusable workflows, matrix builds, macOS\u002FWindows runners, free minutes (2,000\u002Fmo vs Bitbucket's 50 free; Standard 2,500, Premium 3,500)\n- Pipelines wins on: simplicity and zero-config Jira deployment tracking\n\n**Main reason to keep Bitbucket:** native Jira integration — same-vendor, deeper integration than GitHub's, strongest reason Atlassian-centric orgs stay\n\n### 2.6 Confluence\n\n**Key capabilities:**\n- Spaces with a permission model (space admin; page view\u002Fadd\u002Fedit\u002Fdelete\u002Fexport)\n- Page hierarchy and restrictions\n- Fabric editor with macros (code, ToC, panels, status, live Jira issue lists, children display, excerpt\u002Fexcerpt-include)\n- **Whiteboards** (GA February 29, 2024): Cloud-only\n- **Databases** (broad rollout July 10, 2024): structured data as fields + entries, sync from Jira\u002FConfluence\u002FCSV — Cloud-only\n- CQL search and Confluence Analytics (Cloud)\n- Page properties + reports for lightweight tracking\n\n**Confluence vs Notion vs SharePoint:**\n- Confluence wins: Atlassian-integrated teams (live Jira embeds, JSM knowledge base, space permissions)\n- Notion wins: flexible databases\u002FUX for smaller teams\n- SharePoint wins: Microsoft 365-centric document governance\n\n### 2.7 Forge vs Connect\n\n**Forge has replaced Connect** as the app platform.\n\n| | Connect | Forge |\n|---|---|---|\n| Model | External iframe (third-party servers) | Serverless on Atlassian infrastructure |\n| Storage | External DB | Key-value + Forge SQL |\n| Compliance | Requires vendor trust | Preferred model (Atlassian-hosted) |\n| Status | **End of support Q4 2026** | Active, all new investment |\n\n**Connect deprecation timeline:**\n- No new Connect listings: September 17, 2025 — **PASSED**\n- No Connect updates: March 31, 2026\n- End of support: Q4 2026\n\n**Action required:** audit Connect app dependencies; confirm vendors have Forge versions before Q4 2026.\n\n### 2.8 Atlassian Guard (Security Layer)\n\n- **Guard Standard** (SSO\u002FSCIM\u002FAPI-token control\u002Faudit log) — included free in Cloud Enterprise\n- **Guard Premium** (data classification, content scanning\u002FDLP, anomalous-activity threat detection, extended audit) — currently supports Jira and Confluence\n\n---\n\n## Part 3 — GitHub ↔ Atlassian Integration\n\n### The Official \"GitHub for Jira\" App\n\n- Atlassian-maintained; **Jira Cloud only**\n- Links commits\u002Fbranches\u002FPRs\u002Fbuilds\u002Fdeployments to issues by string-matching the Jira issue key\n- Surfaces data in the Jira development panel, board card icons, Code\u002FReleases\u002FDeployments tabs, JQL\n- Smart commits: `PROJ-123 #comment ... #time 2h #done`\n- \"Create branch\" button in Jira; JQL queries over development data\n\n**Limitation:** only as reliable as naming discipline — which is why mature teams enforce issue-keyed branch names via rulesets and drive status transitions via Actions.\n\n**GitHub Enterprise Server ↔ Jira DC:** not supported by the native app — requires third-party (e.g., GitKraken's Git Integration for Jira).\n\n### Production Integration Pattern (50–500 Engineers)\n\n1. **Enforce issue-keyed branch names** via GitHub rulesets (regex rejecting non-conforming branches at push)\n2. **Drive Jira status transitions from GitHub Actions** on `pull_request`\u002F`push`\u002Fdeployment events calling the Jira API or `atlassian\u002Fgajira-*` actions — more reliable than smart commits (which depend on developer discipline and email matching)\n3. **Track deployments** via GitHub Environments → Jira deployment panel\n4. **Pipe CodeQL\u002FDependabot findings into Jira** as security issues via Actions for SLA-tracked remediation\n5. **Keep Jira as system of record;** use GitHub Projects only for engineering-local sprint views to avoid dual-maintenance\n\n---\n\n## Part 4 — Cross-Cutting Concerns\n\n### Org Design\n- Mono-repo vs poly-repo drives GitHub org\u002Fteam structure and Jira project layout (one project per team is the common default)\n- Standardize naming across both: branch names, PR titles, Jira summaries\n- Standardize identity: one IdP (Entra ID\u002FOkta) → GitHub teams via EMU SCIM → Jira groups\u002Froles via Guard SCIM\n\n### End-to-End Agile Delivery Flow\nJira issue → issue-keyed branch → PR (linked) → CI (Actions\u002FPipelines) → human + Copilot code review → merge queue → Jira transition → release → deployment tracked in Jira\n\n- **Dual-track agile:** Confluence (discovery) + Jira sprints (delivery)\n- **DoD enforcement:** Jira automation + GitHub required checks\n\n### DORA Metrics Cross-Platform\n- **Deployment frequency:** GitHub releases\u002Fdeployments\n- **Lead time:** Jira create → PR merge → deploy\n- **Change failure rate:** bug\u002Fincident tickets\n- **MTTR:** incident resolution\n- **Tooling:** LinearB, Sleuth, Faros AI, Jellyfish, Haystack\n\n### Security and Compliance Integration\n- GHAS findings → Jira security issues (via Actions)\n- Both audit logs → SIEM\n- JSM change requests linked to GitHub PRs\u002Fdeployments\n- Secret-scanning alerts → JSM incidents\n- Both platforms carry SOC 2 \u002F ISO 27001; Atlassian Cloud adds FedRAMP\n\n### Licensing and Cost Optimization\n| Product | Standard | Premium |\n|---|---|---|\n| Jira | ~$7.91\u002Fuser\u002Fmo | ~$14.54\u002Fuser\u002Fmo |\n| Confluence | ~$5.42\u002Fuser\u002Fmo | ~$10.44\u002Fuser\u002Fmo |\n| JSM | ~$20\u002Fagent\u002Fmo | ~$47–53\u002Fagent\u002Fmo |\n| GitHub Team | $4\u002Fuser\u002Fmo | — |\n| GitHub Enterprise | ~$21\u002Fuser\u002Fmo | — |\n| GHAS Secret Protection | $19\u002Fcommitter\u002Fmo | — |\n| GHAS Code Security | $30\u002Fcommitter\u002Fmo | — |\n| Copilot Business | $19\u002Fuser\u002Fmo | — |\n| Copilot Enterprise | $39\u002Fuser\u002Fmo (+ GHEC) | — |\n\n**Optimization levers:**\n- Prune inactive users (metered billing means unused seats still cost)\n- Scope GHAS to specific repos, not org-wide\n- Reconcile licenses against IdP group sync\n- Consolidate on Enterprise where volume discounts apply\n- Set Copilot spend alerts given usage-based billing\n\n---\n\n## Staged Implementation Roadmap\n\n### Stage 1 — Stabilize Identity and Deprecation Exposure (Now)\n1. **Migrate Bitbucket app passwords to API tokens\u002FOIDC before June 9, 2026 brownouts** — this is the most urgent hard deadline\n2. Audit Connect app dependencies; confirm vendors have Forge versions before Q4 2026\n3. Standardize SSO\u002FSCIM on one IdP feeding both ecosystems\n4. Decide **EMU vs standard GHEC** using the OSS-contribution and data-residency tests\n\n### Stage 2 — Modernize Governance (Next Quarter)\n1. Migrate branch protection → **organization rulesets** in evaluate mode first, then enforce; add metadata rules for issue-keyed branch names\n2. Enable **merge queue** on busy default branches (remember the `merge_group` trigger)\n3. Scope **GHAS Secret Protection + Code Security** to active repos; turn on push protection org-wide with delegated bypass\n\n### Stage 3 — Integrate and Measure (6–12 Months)\n1. Deploy GitHub for Jira; replace smart-commit reliance with Actions-driven transitions\n2. Stand up DORA metrics via a cross-platform tool\n3. Pilot **Copilot coding agent \u002F code review** and **Rovo agents** on contained workflows; set spend alerts\n\n### Thresholds That Change the Plan\n- Cross ~30 engineers or need workflow gates\u002Fportfolio reporting → move planning to Jira (not GitHub Projects)\n- Active-committer count balloons with bots\u002Fcontractors → re-scope GHAS repos to control cost\n- Copilot agentic usage drives credit overages → cap org spend and restrict premium models\n- Air-gapped\u002Fsovereign requirements → GHES + Bitbucket DC (until 2029)\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdevsecops-cicd\u002Fskills\u002Fgithub-atlassian",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 github-atlassian",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill github-atlassian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill github-atlassian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fdevsecops-cicd\u002Fskills\u002Fgithub-atlassian\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",[],[]]