[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YJ78ST0QDRKTAB3TS5JQS":3,"skill-same:01M72YJ78ST0QDRKTAB3TS5JQS":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":31,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M72YJ78ST0QDRKTAB3TS5JQS","conventional-commits",null,"Create Conventional Commits and PR titles that pass Cocogitto validation. Use when the user asks to commit, stage changes, split commits, write a commit message, open or update a PR title, or prepare squash-merge history.","marcioaltoe\u002Fskills","marcioaltoe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1562865?v=4","01M72Y3750J2CG00P0H2AHDRSZ","Marcio Altoé","01M72Y37642F46H36R4E4S7BNA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F07-evidence-delivery\u002Fconventional-commits\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: conventional-commits\ndescription: Create Conventional Commits and PR titles that pass Cocogitto validation. Use when the user asks to commit, stage changes, split commits, write a commit message, open or update a PR title, or prepare squash-merge history.\nmetadata:\n  category: git\n  tags: [git, github, workflow, communication, documentation]\n  version: 0.1.0\n  author: Marcio Altoé\n  source: https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\n---\n\n# Conventional Commits\n\nCreate commits and PR titles that are easy to review and pass `cog verify`.\n\n## Required format\n\nUse Conventional Commits:\n\n```text\ntype(scope): imperative subject\n```\n\nThe scope is optional:\n\n```text\nfix: handle empty setup files\nfeat(setups): add rust CLI preset\ndocs(readme): clarify setup install commands\n```\n\n## Allowed types\n\n- `feat` - user-facing feature or capability\n- `fix` - bug fix\n- `refactor` - code change without behavior change\n- `docs` - documentation only\n- `test` - tests only\n- `chore` - maintenance without runtime behavior change\n- `build` - build tooling, dependencies, or packaging\n- `ci` - CI workflow changes\n- `perf` - performance improvement\n- `style` - formatting only, not visual UI changes\n- `revert` - revert a previous change\n\n## Subject rules\n\n- Use imperative mood: `add`, `fix`, `remove`, `rename`; not `added`, `fixed`, `removes`.\n- Start lowercase after the colon.\n- Do not end with a period.\n- Keep the first line under 72 characters when possible.\n- Describe the intent, not the file names.\n\n## Commit workflow\n\n1. Inspect the working tree:\n   - `git status --short`\n   - `git diff --stat`\n   - `git diff`\n\n2. Decide commit boundaries.\n   - Split unrelated changes into separate commits.\n   - Split behavior, tests, docs, formatting, dependencies, and generated files when they are reviewable separately.\n   - If one file has mixed changes, use patch staging.\n\n3. Stage only intended changes.\n   - Use `git add \u003Cpath>` for clean file boundaries.\n   - Use `git add -p` for mixed hunks.\n   - Review staged content with `git diff --cached`.\n\n4. Write the message.\n   - Choose the type from the allowed list.\n   - Add a scope when it helps review, usually the package, module, collection, or feature.\n   - Add a body only when the reason is not obvious.\n   - Use footers for `BREAKING CHANGE:`, `Refs #123`, or `Closes #123`.\n\n5. Validate when Cocogitto is available.\n   - `cog verify \"$(git log -1 --pretty=%B)\"`\n   - For a proposed title: `cog verify \"$PR_TITLE\"`\n\n6. Run the smallest relevant verification before committing, or use the repo's required verification command when one exists.\n\n## PR title rules\n\nPull request titles must also use Conventional Commits because squash merge often uses the PR title as the final commit message.\n\nBefore opening or editing a PR:\n\n```bash\nPR_TITLE='feat(setups): add Go CLI preset'\ncog verify \"$PR_TITLE\"\n```\n\nIf `cog` is not installed, still write the title in the exact Conventional Commit format and expect CI to validate it.\n\n## Examples\n\nGood:\n\n```text\nfeat(auth): add token refresh flow\n```\n\nGood with body:\n\n```text\nfix(cli): handle empty setup files\n\nThe installer previously treated an empty setup file as a successful install.\nThis now fails early with a clear error.\n```\n\nBad:\n\n```text\nupdate files\n```\n\nBad:\n\n```text\nfix: change setup line 42\n```\n\n## Output\n\nWhen asked to commit, report:\n\n- commit boundaries chosen\n- staged files for each commit\n- final commit message\n- verification command and result\n","# Conventional Commits\n\nCreate commits and PR titles that are easy to review and pass `cog verify`.\n\n## Required format\n\nUse Conventional Commits:\n\n```text\ntype(scope): imperative subject\n```\n\nThe scope is optional:\n\n```text\nfix: handle empty setup files\nfeat(setups): add rust CLI preset\ndocs(readme): clarify setup install commands\n```\n\n## Allowed types\n\n- `feat` - user-facing feature or capability\n- `fix` - bug fix\n- `refactor` - code change without behavior change\n- `docs` - documentation only\n- `test` - tests only\n- `chore` - maintenance without runtime behavior change\n- `build` - build tooling, dependencies, or packaging\n- `ci` - CI workflow changes\n- `perf` - performance improvement\n- `style` - formatting only, not visual UI changes\n- `revert` - revert a previous change\n\n## Subject rules\n\n- Use imperative mood: `add`, `fix`, `remove`, `rename`; not `added`, `fixed`, `removes`.\n- Start lowercase after the colon.\n- Do not end with a period.\n- Keep the first line under 72 characters when possible.\n- Describe the intent, not the file names.\n\n## Commit workflow\n\n1. Inspect the working tree:\n   - `git status --short`\n   - `git diff --stat`\n   - `git diff`\n\n2. Decide commit boundaries.\n   - Split unrelated changes into separate commits.\n   - Split behavior, tests, docs, formatting, dependencies, and generated files when they are reviewable separately.\n   - If one file has mixed changes, use patch staging.\n\n3. Stage only intended changes.\n   - Use `git add \u003Cpath>` for clean file boundaries.\n   - Use `git add -p` for mixed hunks.\n   - Review staged content with `git diff --cached`.\n\n4. Write the message.\n   - Choose the type from the allowed list.\n   - Add a scope when it helps review, usually the package, module, collection, or feature.\n   - Add a body only when the reason is not obvious.\n   - Use footers for `BREAKING CHANGE:`, `Refs #123`, or `Closes #123`.\n\n5. Validate when Cocogitto is available.\n   - `cog verify \"$(git log -1 --pretty=%B)\"`\n   - For a proposed title: `cog verify \"$PR_TITLE\"`\n\n6. Run the smallest relevant verification before committing, or use the repo's required verification command when one exists.\n\n## PR title rules\n\nPull request titles must also use Conventional Commits because squash merge often uses the PR title as the final commit message.\n\nBefore opening or editing a PR:\n\n```bash\nPR_TITLE='feat(setups): add Go CLI preset'\ncog verify \"$PR_TITLE\"\n```\n\nIf `cog` is not installed, still write the title in the exact Conventional Commit format and expect CI to validate it.\n\n## Examples\n\nGood:\n\n```text\nfeat(auth): add token refresh flow\n```\n\nGood with body:\n\n```text\nfix(cli): handle empty setup files\n\nThe installer previously treated an empty setup file as a successful install.\nThis now fails early with a clear error.\n```\n\nBad:\n\n```text\nupdate files\n```\n\nBad:\n\n```text\nfix: change setup line 42\n```\n\n## Output\n\nWhen asked to commit, report:\n\n- commit boundaries chosen\n- staged files for each commit\n- final commit message\n- verification command and result\n",{"name":5,"metadata":24,"description":7},{"tags":25,"author":12,"source":31,"version":32,"category":26},[26,27,28,29,30],"git","github","workflow","communication","documentation","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills","0.1.0","main","dea450cfd9df78b5cf721964ef178a75cea55cbb","skills\u002F07-evidence-delivery\u002Fconventional-commits",2,"https:\u002F\u002Fmarcioaltoe.github.io\u002Fskills\u002F","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe","Senior Software Engineer · Backend, Systems & AI","2026-11-14 18:29:56",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add marcioaltoe\u002Fskills --skill conventional-commits",{"tool":47,"command":48},"bunx","bunx skills add marcioaltoe\u002Fskills --skill conventional-commits",{"tool":50,"command":51},"pnpm","pnpm dlx skills add marcioaltoe\u002Fskills --skill conventional-commits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F07-evidence-delivery\u002Fconventional-commits\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcommit-message-template.md","REFERENCE","参考文档",498,"https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F07-evidence-delivery\u002Fconventional-commits\u002Freferences\u002Fcommit-message-template.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M72YNVSF4JTTQG3YTR9QNT4Z","startup-validator","Comprehensive startup idea validation and market analysis tool. Use when users need to evaluate a startup idea, assess market fit, analyze competition, validate problem-solution fit, or determine market positioning. Triggers include requests to \"validate my startup idea\", \"analyze market opportunity\", \"check if there's demand for\", \"research competition for\", \"evaluate business idea\", or \"see if my idea is viable\". Provides data-driven analysis using web search, market frameworks, competitive research, and positioning recommendations.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fstartup-validator\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M72YNN34B4MYKEX1X6BB1NS1","positioning-icp","When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' or 'competitive positioning.' This skill covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products. Do NOT use for technical implementation, code review, or software architecture.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fpositioning-icp\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M72YNG8XJ4RHRB5DQMCY9C1N","copywriting","When the user wants to write or rewrite page copy (homepage, landing, pricing, feature), or asks which headline, promise, or message to lead with. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for. Claims must be supportable; a declined claim names the evidence that would unlock it. No AI tells like 'it's not X, it's Y' or 'no X, no Y, no Z'. For editing, see copy-editing. For emails, see emails. For the offer, see offers.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fcopywriting\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72YNBF4JMQ4VCFHTW0WS6SD","business-storyteller","Transforms technical work into persuasive business-language documents for non-technical stakeholders, including internal announcements, approval proposals, incident explainers, technical-debt cases, product explainers, and investor or partner memos. Use when the user asks to present technical work to the company, explain software to business teams, write a business case, make an approval document, or convert a technical artifact into stakeholder communication in the requested language. Do not use for READMEs, specs, ADRs, external marketing pages, or customer-facing sales copy.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbusiness-storyteller\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M72YN8NQ6QR0GHX2A8YW2K4T","brand-storytelling","Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbrand-storytelling\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M72YN3CJH7CKPF4AXNY79Q9S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FSKILL.md",[],[]]