git-issue-sync
Skill0 starsChanged 3 months agoMITView on GitHub
Audit git history against GitHub Issues to find untracked work and ensure compliance (sync issues, find untracked commits, issue compliance).
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-protocolSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- pr-workflowSkill
- rapid-builderSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- unstuckSkill
- ux-design-systemSkill
- ux-researchSkill
- webapp-testingSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Add progress comments to open issues related to current work
- Very specific: line 60
Every open PR must reference an issue via Closes #N or Fixes #N
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Issue Compliance Audit
Pre-fetched State
Working Directory
!git status --porcelain 2>/dev/null || echo "Not a git repository"
Last 20 Commits
!git log --oneline -20 2>/dev/null
Open Issues
!gh issue list --state open --limit 50 --json number,title,labels 2>/dev/null || echo "No GitHub CLI or repo"
Recently Closed Issues
!gh issue list --state closed --limit 20 --json number,title,closedAt 2>/dev/null || echo "None"
Open PRs
!gh pr list --state open 2>/dev/null || echo "None"
All Branches
!git branch -a 2>/dev/null
Your Task
Using the pre-fetched data above:
1. Find Untracked Work
- Identify commits that don't reference an issue number (#N)
- Identify modified files with no associated issue
- Flag commits missing conventional format
2. Create Missing Issues
For every untracked piece of work, create an issue:
gh issue create \
--title "[TYPE] Description" \
--body "$(printf '## Description\n[What was done]\n\n## Commits\n- SHA: [description]')" \
--label "type/[TYPE]" \
--label "priority/[P0|P1|P2]" \
--label "area/[AREA]"3. Update Existing Issues
- Add progress comments to open issues related to current work
- Close completed issues with
gh issue close N -c "..." - Link commits to issues retroactively in comments
4. PR Audit
- Every open PR must reference an issue via
Closes #NorFixes #N - Flag PRs without linked issues
5. Branch Hygiene
- Orphaned branches without associated issues
- Branches with no activity in 14+ days
- Names not following
feature/orhotfix/convention
6. Report
- Total work items identified
- Issues created this session
- Issues updated
- Non-compliant commits (no issue reference)
- PR linkage status
- Compliance score (%)
Push all issue updates to GitHub immediately.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

