github-publishing-workflow
Skill1 starsChanged 3 months agoMITView on GitHub
GitHub Release, Publishing & CI/CD Automation Playbook. Integrates Conventional Commits (git-commit), GitHub Actions Workflows (create-github-action-workflow-specification), GitHub Issues & Release Triage (github-issues), Semantic Versioning, Package/Binary Publishing, and Automated Release Gates.
- Reads credentials
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- autoresearchSkill
- brainstormingSkill
- brandkitSkill
- create-github-action-workflow-specificationSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- dispatching-parallel-agentsSkill
- dokion-hardeningSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- full-output-enforcementSkill
- git-commitSkill
- github-publishing-workflowSkill
- google-ai-studio-web-editorSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- industrial-brutalist-uiSkill
- minimalist-uiSkill
- receiving-code-reviewSkill
- redesign-existing-projectsSkill
- requesting-code-reviewSkill
- stitch-design-tasteSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- ui-ux-design-engineSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
- autoresearchSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- dokion-hardeningSkill
- agent-playbookSkill
- archifySkill
- autoresearchSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- dokion-automationSkill
- dokion-fullstackSkill
- dokion-hardeningSkill
- dokion-playbook-creatorSkill
- dokion-playbook-hubSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- google-ai-studio-web-editorSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
All commits MUST follow the Conventional Commit specification: <type>(<scope>): <short summary>.
- Distinctive: line 17
Commit messages must be imperatively phrased, lowercase summary, no trailing period.
- Very specific: line 31
Never publish to npm, GitHub Packages, or GitHub Releases without passing all automated verification gates (typecheck, test, lint, build).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitHub Publishing & CI/CD Automation Playbook
This playbook defines the standardized operational workflow for publishing releases, managing GitHub Issues, authoring secure GitHub Actions workflows, and enforcing Conventional Commits across GitHub repositories.
1. Core Principles & Skill Integrations
- Conventional Commits & Semantic Versioning (
git-commit):- All commits MUST follow the Conventional Commit specification:
<type>(<scope>): <short summary>. - Types:
feat(minor version bump),fix(patch version bump),BREAKING CHANGE:(major version bump),docs,chore,refactor,perf,test. - Commit messages must be imperatively phrased, lowercase summary, no trailing period.
- All commits MUST follow the Conventional Commit specification:
- GitHub Actions Workflow Standards (
create-github-action-workflow-specification):- Least-privilege GITHUB_TOKEN permissions (
permissions: { contents: read }). - Pinned action versions with SHA or major release tags (
actions/checkout@v4,oven-sh/setup-bun@v2). - Built-in dependency caching (
cache: 'bun'orcache: 'npm'). - Matrix builds for cross-platform/node/bun verification (macOS, Ubuntu, Windows).
- Least-privilege GITHUB_TOKEN permissions (
- GitHub Issues & Release Triage (
github-issues):- Automated issue linking via commit messages (
Fixes #123,Closes #456). - Categorized release notes generation (Features, Fixes, Breaking Changes, Maintenance).
- Label & milestone assignment during release lifecycle.
- Automated issue linking via commit messages (
- Zero Unverified Releases:
- Never publish to npm, GitHub Packages, or GitHub Releases without passing all automated verification gates (
typecheck,test,lint,build).
- Never publish to npm, GitHub Packages, or GitHub Releases without passing all automated verification gates (
2. Conventional Commit Specification (git-commit)
# Feature addition (triggers MINOR version bump v1.1.0)
git commit -m "feat(autopilot): add bounded retry scheduler with exponential backoff"
# Bug fix (triggers PATCH version bump v1.0.1)
git commit -m "fix(cli): resolve permission denial on custom playbook activation"
# Breaking change (triggers MAJOR version bump v2.0.0)
git commit -m "feat(api)!: migrate state schema to v2 event chain
BREAKING CHANGE: The state.json schema v1 is deprecated. Migrations are performed automatically."3. Production GitHub Actions Workflow (.github/workflows/release.yml)
name: CI/CD Release Pipeline
on:
push:
branches: [main]
pull_request:
branches: [main]
release:
types: [published]
permissions:
contents: read
jobs:
verify:
name: Verify & Test
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v4
- name: Setup Bun Environment
uses: oven-sh/setup-bun@v2
with:
bun-version: latest
- name: Install Dependencies
run: bun install --frozen-lockfile
- name: Run Typecheck
run: bun run typecheck
- name: Run Linter
run: bun run lint
- name: Run Test Suite
run: bun test
- name: Verify Production Build
run: bun run build
publish:
name: Publish Release Artifacts
needs: verify
if: github.event_name == 'release'
runs-on: ubuntu-latest
permissions:
contents: write
id-token: write # Required for npm provenance / OIDC
steps:
- name: Checkout Code
uses: actions/checkout@v4
- name: Setup Bun Environment
uses: oven-sh/setup-bun@v2
with:
bun-version: latest
- name: Install Dependencies
run: bun install --frozen-lockfile
- name: Build Distribution Bundle
run: bun run build
- name: Publish to NPM / GitHub Packages
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: npm publish --access public --provenance4. Execution Workflow (Sequential Pipeline)
graph TD
A[1. Audit & Lint Git Commit Messages] --> B[2. Check & Validate GitHub Actions Workflows]
B --> C[3. Triage & Link GitHub Issues & Pull Requests]
C --> D[4. Execute Release Gates: typecheck, lint, test, build]
D --> E[5. Bump Semantic Version & Generate Release Notes]
E --> F[6. Publish Release Artifacts to GitHub / Package Registry]5. Release Checklist
- All commit messages since last tag conform to Conventional Commits.
- GitHub Actions workflow
.github/workflows/release.ymlsyntax validated. - Minimal token permissions (
contents: read/contents: write) enforced. - All open issues linked to the release milestone triaged.
- All verification commands (
bun test,bun run typecheck,bun run lint,bun run build) passed with zero errors. - Package distribution dry-run (
npm publish --dry-runorbun pm pack) verified.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

