git-workflow
Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- git-workflow
- license
- MIT
- metadata
- { "author": "antigravity-team", "version": "2.0" }
- description
- Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
- allowed-tools
- Read, Glob, Grep, Edit, Write, Bash
02 资源文件 1
- 参考文档skill-report.json20.7 KB
03 SKILL.md 正文
Git Workflow
커밋부터 완료 검증까지의 Git 워크플로우 통합 스킬입니다.
Conventional Commits
Format
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | 설명 | 예시 |
|---|---|---|
feat |
새 기능 | feat(auth): add JWT login |
fix |
버그 수정 | fix(api): handle null response |
refactor |
리팩토링 | refactor(utils): simplify parser |
docs |
문서 | docs: update README |
test |
테스트 | test(auth): add login tests |
chore |
기타 | chore: update deps |
Breaking Changes
feat(api)!: change response format
BREAKING CHANGE: response.data is now response.result
Pre-Completion Verification
완료 선언 전 필수 체크
# 1. 테스트 통과
npm test
# 2. 린트 통과
npm run lint
# 3. 타입 체크 (TypeScript)
npx tsc --noEmit
# 4. 빌드 성공
npm run build
Verification Checklist
- [ ] 모든 테스트 통과
- [ ] 린트 에러 없음
- [ ] 타입 에러 없음
- [ ] 빌드 성공
- [ ] 변경사항 커밋됨
- [ ] 불필요한 console.log 제거
Branch Strategy
main ─────────────────────────────
│
└─ feature/auth ───○───○───○─┐
│
└─ merge
Naming
feature/<description>
fix/<issue-number>-<description>
refactor/<description>
Commit Workflow
# 1. 변경사항 스테이징
git add <files>
# 2. 커밋 (규격 준수)
git commit -m "feat(scope): description"
# 3. 푸시 전 검증
npm test && npm run lint
# 4. 푸시
git push
Checklist
- [ ] 커밋 메시지 규격 준수
- [ ] 테스트 통과
- [ ] 린트 통과
- [ ] 빌드 성공
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.