rsyslog-commit

0
0
Source

Ensures compliance with rsyslog's strict commit message and branching policies.

Install

mkdir -p .claude/skills/rsyslog-commit && curl -L -o skill.zip "https://mcp.directory/api/skills/download/6276" && unzip -o skill.zip -d .claude/skills/rsyslog-commit && rm skill.zip

Installs to .claude/skills/rsyslog-commit

About this skill

rsyslog_commit

This skill standardizes the final step of the development workflow: committing and contributing.

Quick Start

  1. Format First: Run devtools/format-code.sh.
  2. Commit Message: Follow the 62/72 rule and the mandatory "Why" structure.
  3. Attribution: Include the AI-Agent footer.

Detailed Instructions

1. Pre-Commit Checklist

  • Code Style: Run bash devtools/format-code.sh IF any .c or .h files were modified. This is mandatory for C source changes.
  • Validation: Ensure make -j$(nproc) check TESTS="" passes and relevant tests are run.
    • Multi-Pass AI Audit: Run the /audit workflow for a rigorous, persona-based review (Memory, Concurrency, Standards) using the project's canned prompts.
    • Mock Smoke Check: If you added or renamed test files, run make distcheck TEST_RUN_TYPE=MOCK-OK -j$(nproc) as a final distribution check.
    • Note: If you already successfully built and tested your changes immediately before formatting, you do NOT need to re-run the build/test cycle. Formatting is a normalization step and does not affect functionality.

2. Commit Message Structure

Rsyslog requires rich, structured commit messages (plain ASCII).

  • Title: <component>: <action> (Max 62 characters).
  • Body: Max 72 characters per line.
  • GitHub Issues: Use full URLs (e.g., https://github.com/rsyslog/rsyslog/issues/883) instead of shorthand #883.
  • Mandatory Sections:
    • Why: Brief non-technical rationale.
    • Impact: One line if behavior/tests changed.
    • Before/After: One-line summary.
    • Technical Overview: 4–12 lines describing the change conceptually.
  • AI Footer: With the help of AI-Agents: <agent-name>

3. Using the Assistant

4. Branching & PRs

  • Base Branch: Always target main.
  • Naming: i-<issue-number> or <agent-name>-i-<issue-number>.
  • Target: PRs must target rsyslog/rsyslog directly.

Related Skills

  • rsyslog_build: To verify the code before committing.
  • rsyslog_test: To provide validation metrics for the commit message.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

641968

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

590705

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

339397

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318395

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

450339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.