project-conventions

Enforce Polibase project conventions during commits, PRs, and CI/CD failures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/trust-chain-organization/polibase --skill project-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/trust-chain-organization/polibase/tree/main/.claude/skills/project-conventions
Command: npx skills add https://github.com/trust-chain-organization/polibase --skill project-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solves? This Skill standardizes development practices across the Polibase project, eliminating inconsistencies and ensuring high code quality. It automates the enforcement of critical rules like pre-commit hooks and CI/CD guidelines, reducing manual review effort and preventing common errors.

Core Features & Use Cases

  • Pre-commit Hook Enforcement: Guides on adhering to pre-commit hooks (Ruff, Pyright, Prettier) to maintain code style and quality.
  • CI/CD Best Practices: Provides rules for managing CI/CD test skips, ensuring proper issue creation and tracking.
  • File Management: Directs the proper placement of temporary files (tmp/) and knowledge accumulation (_docs/), keeping the repository clean and organized.
  • Use Case: When you're about to commit code, this skill automatically checks if your changes comply with all project conventions, such as formatting, linting, and type checking, preventing CI/CD failures and ensuring your code is ready for review.

Quick Start

I am about to commit my changes. Check if my code adheres to all Polibase project conventions and pre-commit hook rules.

Frequently Asked Questions about project-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent CI/CD failures by enforcing code quality checks before committing?

Pre-commit hook enforcement automatically runs linting, type checking, and formatting tools (Ruff, Pyright, Prettier) on your changes before commit creation, catching violations early and preventing non-compliant code from reaching CI/CD pipelines.

What are Polibase project conventions and why do they matter?

Project conventions are standardized development rules—pre-commit hooks, linting standards, type checking, and file organization—that eliminate inconsistencies across the codebase, reduce manual review effort, and ensure high code quality across all contributions.

How should I organize temporary files and documentation in my commits?

Place temporary files in the `tmp/` directory and knowledge accumulation in the `_docs/` directory to keep the repository clean and organized according to Polibase conventions, preventing clutter and maintaining structural consistency.

Can I skip CI/CD tests, and what's the proper way to handle test failures?

CI/CD test skips must follow project guidelines and require proper issue creation and tracking; skipping tests without documented justification violates conventions and should be avoided to maintain code quality gates.

Do pre-commit hooks work with my existing development workflow?

Pre-commit hooks integrate directly into the commit creation process, activating automatically when you attempt to commit; they work with standard Git workflows and require no additional setup beyond initial configuration.