git:status
Skill303 starsChanged 4 months agoApache-2.0View on GitHub
Show worktrees with PR status and TODO files overview
In this repository110 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auth:keycloak-confidential-clientSkill
- auth:mlflow-oidc-authSkill
- auth:otel-oauth2-exporterSkill
- authSkill
- ci:monitoringSkill
- ciSkill
- ci:statusSkill
- cve:brainstormSkill
- cve:scanSkill
- cveSkill
- design:reviewSkill
- designSkill
- docs:reviewSkill
- genai:semantic-conventionsSkill
- genaiSkill
- git:commitSkill
- github:dependabotSkill
- github:issuesSkill
- github:last-week-orgSkill
- github:last-weekSkill
- github:my-statusSkill
- github:prsSkill
- githubSkill
- github:streamerSkill
- git:rebaseSkill
- gitSkill
- git:worktreeSkill
- graph-loopSkill
- helm:debugSkill
- helmSkill
- hypershift:clusterSkill
- hypershift:debugSkill
- hypershift:preflightSkill
- hypershift:quotasSkill
- hypershift:setupSkill
- hypershiftSkill
- istio:ambient-waypointSkill
- istio:mesh-selfhealSkill
- istioSkill
- k8s:healthSkill
- k8s:live-debuggingSkill
- k8s:logsSkill
- k8s:podsSkill
- k8sSkill
- kind:clusterSkill
- kindSkill
- local:full-testSkill
- localSkill
- local:testingSkill
- metaSkill
- meta:write-docsSkill
- onboard:linkSkill
- onboardSkill
- onboard:standardsSkill
- openshift:debugSkill
- openshift:routesSkill
- openshiftSkill
- openshift:trusted-ca-bundleSkill
- orchestrate:ciSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run these commands to get full project status:
≈ “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 Status
Show comprehensive status of worktrees, their PRs, and TODO files.
Quick Status
Run these commands to get full project status:
# 1. Worktrees with PR status
echo "=== Worktrees ===" && \
git worktree list --porcelain | grep -E "^worktree|^branch" | paste - - | \
while read wt branch; do
dir=$(echo "$wt" | sed 's/worktree //')
br=$(echo "$branch" | sed 's|branch refs/heads/||')
pr=$(gh pr list --head "$br" --json number,state,title --jq '.[0] | "PR #\(.number) [\(.state)]"' 2>/dev/null || echo "No PR")
printf "%-50s %-30s %s\n" "$dir" "$br" "$pr"
done
# 2. TODO files
echo "" && echo "=== TODO Files ===" && \
ls -1 TODO_*.md 2>/dev/null | while read f; do
title=$(head -1 "$f" | sed 's/^# //')
printf "%-40s %s\n" "$f" "$title"
doneDetailed Worktree Status
# Show worktrees with full PR details
git worktree list | while read dir commit branch; do
branch=$(echo "$branch" | tr -d '[]')
echo "=== $branch ==="
echo " Path: $dir"
gh pr list --head "$branch" --json number,title,state,url,statusCheckRollup \
--jq '.[] | " PR #\(.number): \(.title)\n State: \(.state)\n URL: \(.url)\n Checks: \([.statusCheckRollup[]? | .conclusion] | group_by(.) | map("\(.[0]): \(length)") | join(", "))"' 2>/dev/null || echo " No PR"
echo ""
donePR Status Only
# Quick PR status for open PRs by author
gh pr list --author @me --state open \
--json number,title,headRefName,statusCheckRollup \
--jq '.[] | "PR #\(.number) [\(.headRefName)]: \([.statusCheckRollup[]? | select(.conclusion == "FAILURE")] | length) failures"'TODO Files Overview
# List TODO files with first line (title)
for f in TODO_*.md; do
[ -f "$f" ] && printf "%-45s %s\n" "$f" "$(head -1 "$f" | sed 's/^# //')"
done
# Find TODO files mentioning specific branch
grep -l "branch-name" TODO_*.md 2>/dev/nullCombined Status Table
For a formatted table output:
echo "| Worktree | Branch | PR | CI Status |"
echo "|----------|--------|----|-----------| "
git worktree list --porcelain | grep -E "^worktree|^branch" | paste - - | \
while read wt branch; do
dir=$(basename "$(echo "$wt" | sed 's/worktree //')")
br=$(echo "$branch" | sed 's|branch refs/heads/||')
pr_info=$(gh pr list --head "$br" --json number,statusCheckRollup \
--jq '.[0] | "#\(.number) \([.statusCheckRollup[]? | select(.conclusion == "FAILURE")] | length) fail"' 2>/dev/null)
[ -z "$pr_info" ] && pr_info="No PR"
echo "| $dir | $br | $pr_info |"
doneRelated Skills
git:worktree- Manage worktreeshypershift:cluster- HyperShift cluster management
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.

