What checks should be completed before submitting?

Run the full quality gate, self-review your diff, ensure primitives for workflow patterns, and verify no secrets are committed.

create-pull-request

npx machina-cli add skill theinterneti/TTA.dev/create-pull-request --openclaw

Files (1)

SKILL.md

1.3 KB

Create Pull Request (TTA.dev)

Guide for creating well-structured pull requests.

PR Title

Follow Conventional Commits format: <type>: <description>

Examples:

feat: add CachePrimitive metrics integration
fix: resolve timeout in RetryPrimitive backoff
docs: update primitives catalog with new skills API

PR Description Template

## Summary
Brief description of what this PR does.

## Changes
- List of specific changes made.

## Testing
- How the changes were tested.
- Coverage impact.

## Checklist
- [ ] Quality gate passes (format, lint, type check, tests)
- [ ] 100% test coverage on new code
- [ ] Documentation updated if applicable
- [ ] No new anti-patterns introduced

Before Submitting

Run the full quality gate (see build-test-verify skill).
Self-review your diff (see self-review-checklist skill).
Ensure all new code uses primitives for workflow patterns.
Verify no secrets or credentials are committed.

Deep Reference

For full Python coding standards, see docs/agent-guides/python-standards.md.

Source

git clone https://github.com/theinterneti/TTA.dev/blob/main/.claude/skills/create-pull-request/SKILL.mdView on GitHub

Overview

This skill guides creating or updating pull requests in the TTA.dev repository. It enforces Conventional Commits for titles, a standardized Markdown PR description, and a practical pre-submit checklist to improve review quality.

How This Skill Works

It enforces a Conventional Commits title, a PR Description Template with sections (Summary, Changes, Testing, Checklist), and a Before Submitting workflow. It also highlights running the full quality gate and avoiding secrets being committed.

When to Use It

Creating a new PR for code or docs changes in the TTA.dev repository
Updating an existing PR with additional commits or fixes
Submitting after implementing tests and ensuring 100% test coverage on new code
Ensuring the PR passes code quality gates (lint, type checks) before submission
Complying with project standards (e.g., Python coding standards) linked in Deep Reference

Quick Start

Step 1: Create a new PR with a title following Conventional Commits
Step 2: Add a PR Description using the Summary/Changes/Testing/Checklist template
Step 3: Run the full quality gate (build-test-verify), perform self-review, ensure no secrets, then submit

Best Practices

Use Conventional Commits for the PR title: '<type>: <description>'
Write a PR description with Summary, Changes, Testing, and Checklist sections
Fill out the Checklist and ensure quality gates (format, lint, type checks, tests) pass
Include 100% test coverage on new code and mention testing approach
Self-review your diff and verify no secrets or credentials are committed

Example Use Cases

feat: add CachePrimitive metrics integration
fix: resolve timeout in RetryPrimitive backoff
docs: update primitives catalog with new skills API
chore: update CI config to run build-test-verify
test: add unit tests for new primitives usage

Frequently Asked Questions

Add this skill to your agents