01-git-workflow
Composable Rust infrastructure crates for building xTax services and applications.
Install / Use
npx skills add cz-jcode/xtaxInstalls into whichever agent you are using.
.clinerules
Cline rules
Quality Score
Category
AutomationSupported Platforms
Our assessment of 01-git-workflow
01-git-workflow scores 53/100 on our quality scale, 2698th of 2,780 Automation skills we index.
Its .clinerules is 1.8 KB long, well organised into 8 sections with 1 code example: moderately detailed.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-11-10 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
01-git-workflow compared with similar skills
All 4 of these similar skills score higher than 01-git-workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 01-git-workflow (this skill)by cz-jcode | 53 | 0 | — | .clinerules |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install 01-git-workflow?
- Run
npx skills add cz-jcode/xtax. The install tabs above show the steps for each supported agent. - Which AI agents does 01-git-workflow work with?
- It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
- Is 01-git-workflow safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is 01-git-workflow still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubGit Workflow for Cline
Purpose: enforce a consistent Rust-style PR workflow for all changes. Every change must go through a feature branch, a conventional commit, and a pull request.
Rules (MUST)
-
Always create a new branch before committing.
- Branch names must be kebab-case:
add-docs-ci-job,fix-blob-encrypt-panic,ci-pin-actions. - Use a descriptive, short name that reflects the change.
- Branch names must be kebab-case:
-
Commit messages must follow conventional commits with a Rust-style prefix:
feat:– new featurefix:– bug fixdocs:– documentation onlyci:– CI/CD changeschore:– maintenance, deps, toolingrefactor:– code change that neither fixes a bug nor adds a featurestyle:– formatting, whitespace (no code change)test:– adding or updating testsperf:– performance improvementbuild:– build system or external dependenciesrevert:– revert a previous commit
-
Push the branch to
origin. -
Create a pull request via
gh pr create:- Use the commit message as the PR title.
- Fill the PR body with a summary of changes.
- Use
--base main. - Reference related issues if applicable.
Example workflow
# 1. Create branch
git checkout -b add-docs-ci-job
# 2. Stage and commit
git add .github/workflows/ci.yml
git commit -m "ci: add docs job to CI workflow"
# 3. Push
git push -u origin add-docs-ci-job
# 4. Create PR
gh pr create \
--base main \
--title "ci: add docs job to CI workflow" \
--body "Build rustdoc for xtax-encryption, xtax-blob-storage, and xtax with --all-features --no-deps, treating warnings as errors."
Reference
- Conventional commits: https://www.conventionalcommits.org/
- Rust commit style often matches conventional commits with lowercase, no trailing punctuation.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
