Skip to content
View shenxianpeng's full-sized avatar

Organizations

@jenkinsci @cpp-linter @commit-check @conventional-branch @devops-maturity @castops @mkdocs-ng

Block or report shenxianpeng

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
shenxianpeng/README.md

Hi, I'm Xianpeng 👋

Profile Views My PyPI packages My PyPI packages stats Sponsor me on GitHub committers.top badge

About | Blog | RSS | Medium | Dev.to | WeChat | Zhihu


I build open-source tools for DevOps, CI/CD, and software delivery — collected under the Open Delivery Stack (ODS) vision: machine-readable governance standards, quality gates, CI intelligence, dependency safety, and engineering insights. AI is increasingly part of this — explaining failures, reviewing changes, and helping teams ship with evidence.

📦 What I Build

Area Problem Projects
Govern delivery with evidence 🚧 AI writes code faster than governance can track; teams need machine-readable evidence at every stage. 📜 spec · 🔧 cli · ✅ validate-action
Code quality & standards Catch C/C++, Jenkinsfile, and Dockerfile issues early; enforce naming and commit conventions. 🔍 cpp-linter-action · 🪝 cpp-linter-hooks · 🌿 conventional-branch · ✅ commit-check · 🏗️ jenkinsfilelint · 🐳 hadolint-pre-commit
CI/CD intelligence AI-powered failure diagnosis, dependency security, and Python version lifecycle awareness. 🤖 explain-error-plugin · 🛡️ pipguard · ⏰ py-eol
Workflows & insights Platform tooling, API integrations, and maturity metrics for engineering teams. ⚙️ cast-cli · 🔗 atlassian-api-py · 📊 gitstats · 📈 devops-maturity

🤖 AI & Current Focus

  • 🚧 Open Delivery Spec (ODS) — machine-readable delivery governance: spec, CLI, and CI validation — every commit-to-deploy stage leaves auditable evidence. (actively building)
  • commit-check — configurable Git commit and branch name validation for teams and CI pipelines.
  • cpp-linter — C/C++ linting, formatting, and static analysis feedback directly in PRs and pre-commit.
  • Explain Error Plugin — AI-powered Jenkins failure diagnosis: causes, explanations, and suggested fixes instead of raw logs.

👥 Community


WeChat: shenxianpeng - sharing AI + DevOps practices and real-world engineering notes.


✍️ Writing

Pinned Loading

  1. cpp-linter/cpp-linter-action cpp-linter/cpp-linter-action Public

    A Github Action for linting C/C++ code integrating clang-tidy and clang-format to collect feedback provided in the form of file-annotations, thread-comments, workflow step-summary, and Pull Request…

    142 23

  2. cpp-linter/cpp-linter-hooks cpp-linter/cpp-linter-hooks Public

    C/C++ pre-commit hooks powered by clang-format and clang-tidy

    Python 44 5

  3. commit-check/commit-check commit-check/commit-check Public

    Commit Check enforces commit metadata standards — commit messages, branch naming, committer info, signoff, and more.

    Python 63 9

  4. conventional-branch/conventional-branch conventional-branch/conventional-branch Public

    The Conventional Branch Specification

    SCSS 107 7

  5. jenkinsci/explain-error-plugin jenkinsci/explain-error-plugin Public

    Explain Jenkins job failures with AI

    Java 40 22

  6. jenkinsci/jenkinsfilelint jenkinsci/jenkinsfilelint Public

    Validate Jenkinsfile syntax locally using pre-commit

    Python 4